[amarok] [Bug 390300] Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
https://bugs.kde.org/show_bug.cgi?id=390300 Myriam Schweingruber changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 390300] Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
https://bugs.kde.org/show_bug.cgi?id=390300 --- Comment #4 from Myriam Schweingruber--- 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. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 390300] Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
https://bugs.kde.org/show_bug.cgi?id=390300 --- Comment #2 from David Muya--- 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_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=390300 > > Myriam Schweingruber changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #1 from Myriam Schweingruber --- > 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. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 390300] Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
https://bugs.kde.org/show_bug.cgi?id=390300 Myriam Schweingruberchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Myriam Schweingruber --- 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 are watching all bug changes.