Bug 390300 - Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
Summary: Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: 2.9
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-12 02:34 UTC by David Muya
Modified: 2018-09-26 07:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
amarok-20180220-042900.kcrash.txt (27.97 KB, text/plain)
2018-02-20 01:41 UTC, David Muya
Details
amarok-20180220-042900.kcrash1.txt (393 bytes, text/plain)
2018-02-20 01:41 UTC, David Muya
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Muya 2018-02-12 02:34:11 UTC
When I launch Amarok, it only shows on the task bar and when I right click and select Restore, it crashes. I'm using Kubuntu 16.04.3LTS with KDE 5.8.8LTS
Comment 1 Myriam Schweingruber 2018-02-17 23:28:14 UTC
We would need a backtrace for that crash, without it this report is pretty useless.

See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Make sure to put the backtrace directly in the comment, not as an attachment as attachments are not searchable in the bug database.
Comment 2 David Muya 2018-02-20 01:41:02 UTC
Created attachment 110829 [details]
amarok-20180220-042900.kcrash.txt

The bug reporting mechanism reports that a useful backtrace could not be
generated. But I managed to get these. Please find attached.

On Sun, Feb 18, 2018 at 2:28 AM, Myriam Schweingruber <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=390300
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |BACKTRACE
>
> --- Comment #1 from Myriam Schweingruber <myriam@kde.org> ---
> We would need a backtrace for that crash, without it this report is pretty
> useless.
>
> See also
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_
> useful_crash_reports
>
> Make sure to put the backtrace directly in the comment, not as an
> attachment as
> attachments are not searchable in the bug database.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 David Muya 2018-02-20 01:41:55 UTC
Created attachment 110830 [details]
amarok-20180220-042900.kcrash1.txt
Comment 4 Myriam Schweingruber 2018-02-23 18:13:34 UTC
Did you read my comment? attaching backtraces is not really helpful...

Anyway, these backtraces are not useful, we need a proper backtrace to be able to do something.