Bug 394498 - Discover crashed on start 3 times
Summary: Discover crashed on start 3 times
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-05-21 02:54 UTC by Colin
Modified: 2018-10-29 02:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Colin 2018-05-21 02:54:42 UTC
discover crashed 4 times when started.
Comment 1 Aleix Pol 2018-05-21 22:56:05 UTC
Can you provide a backtrace or something I can use?
Which distribution would also help and the terminal output too.
Comment 2 Colin 2018-05-22 05:38:25 UTC
I have just downloaded Neptune 5 Plasma5 to a second machine.

HP EliteBook i5-2520M 4Gig memory.

Discover crashed and was the second app I ran.

Prior to that I added Latte.

I note from bug reports this appears to be a common fault.

Regards

Colin

Sent from my iPad

> On 22 May 2018, at 01:56, Aleix Pol <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=394498
> 
> Aleix Pol <aleixpol@kde.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>         Resolution|---                         |BACKTRACE
> 
> --- Comment #1 from Aleix Pol <aleixpol@kde.org> ---
> Can you provide a backtrace or something I can use?
> Which distribution would also help and the terminal output too.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 3 Christoph Feck 2018-06-15 00:13:00 UTC
If this issue is still reproducible, please add the backtrace of the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 4 Andrew Crouthamel 2018-09-28 03:27:32 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:00:35 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!