Bug 382349 - Installed mplayer from Discover, erased a search term, then Discover crashed and won't restart. Kubuntu 17.04
Summary: Installed mplayer from Discover, erased a search term, then Discover crashed ...
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-07-14 19:02 UTC by Gordon Bried
Modified: 2018-10-28 03:40 UTC (History)
0 users

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


Attachments
attachment-2257-0.html (1.18 KB, text/html)
2017-07-16 11:56 UTC, Gordon Bried
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Bried 2017-07-14 19:02:26 UTC
Discover crashes often, just looking up app packages ordisplaying the info box for an app. This crash: I searced for a term found a list of software, installed one, and after finished, I erased the term in the search box and Discover disappeared immediately. Discover would not restart after that.

PS. in auto bug report there is no opportunity to give info about what happened, so what good is that?
Comment 1 Aleix Pol 2017-07-16 00:05:53 UTC
Hi,
Do you have a backtrace for which it's not starting again?
Or can you check if it's still running?
Comment 2 Aleix Pol 2017-07-16 00:06:01 UTC
Hi,
Do you have a backtrace for which it's not starting again?
Or can you check if it's still running?
Comment 3 Gordon Bried 2017-07-16 11:56:03 UTC
Created attachment 106663 [details]
attachment-2257-0.html

Sorry, i don't have a backtrace. Thought it was creating 1 in the auto bug
process, but i don't know where it would be filed.
Discover  mostly crashes after installing an app, when i enter a search
term.

How do i make a backtrace next time?

Cheers


On Jul 15, 2017 5:06 PM, "Aleix Pol" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=382349
>
> --- Comment #2 from Aleix Pol <aleixpol@kde.org> ---
> Hi,
> Do you have a backtrace for which it's not starting again?
> Or can you check if it's still running?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Aleix Pol 2017-07-16 23:20:02 UTC
Dr Konqi (the auto bug process) will attach the backtrace automatically.
If you can easily reproduce it, you can see ubuntu's documentation:
https://wiki.ubuntu.com/Backtrace
Comment 5 Andrew Crouthamel 2018-09-28 02:28:57 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 6 Andrew Crouthamel 2018-10-28 03:40:44 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!