Bug 393791 - program won't start
Summary: program won't start
Status: RESOLVED WORKSFORME
Alias: None
Product: krecipes
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-05-03 06:13 UTC by Dan
Modified: 2018-10-29 02:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2018-05-03 06:13:13 UTC
The contents of your debug file:

Application: krecipes (2.1.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.13.0-39-generic x86_64
Distribution: Linux Mint 18.3 Sylvia

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/
Comment 1 Christoph Feck 2018-05-03 11:24:09 UTC
If the crash is reproducible, please add a backtrace for the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Dan 2018-05-03 11:40:17 UTC
I sent you the contents of the file, it said something like there wasn't 
enough info provided to make a report
Perhaps that is because the program would not open.
Dan


On 05/03/2018 02:24 PM, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=393791
>
> Christoph Feck <cfeck@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |NEEDSINFO
>           Resolution|---                         |BACKTRACE
>
> --- Comment #1 from Christoph Feck <cfeck@kde.org> ---
> If the crash is reproducible, please add a backtrace for the crash. For more
> information, please see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
>
Comment 3 Christoph Feck 2018-05-03 12:03:32 UTC
If you are unable to follow the instructions from comment #1, I suggest to ask for help in the forum of your distribution, see https://forums.linuxmint.com/

Without a backtrace, KDE developers cannot investigate the issue.
Comment 4 Andrew Crouthamel 2018-09-28 03:28:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:08:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!