Summary: | Amarok keeps crashing at each start up. | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Henderikus <hannes68> |
Component: | Collections/USB mass storage and MSC | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | bart.cerneels |
Priority: | NOR | ||
Version: | 2.8.0 | ||
Target Milestone: | 2.9 | ||
Platform: | Mint (Debian based) | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Henderikus
2018-03-07 13:48:02 UTC
We need a proper backtrace, please see also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Hi Myriam,
the crash assistant will not generate a backtrace anymore. It now tells
me to manually file the bug. One information that I can add. Mint is
always running in fall back mode, an issue I am unable to solve untill
present. This does not seem to affect any application, nore system
performance.
Best regards, Henderikus.
__________________________
Myriam Schweingruber schreef op wo 07-03-2018 om 18:12 [+0000]:
> https://bugs.kde.org/show_bug.cgi?id=391522
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
> What |Removed |Added
> -------------------------------------------------------------------
> ---------
> Status|UNCONFIRMED |NEEDSINFO
> Resolution|--- |BACKTRACE
>
> --- Comment #1 from Myriam Schweingruber <myriam@kde.org> ---
> We need a proper backtrace, please see also
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_crea
> te_useful_crash_reports
>
why do you even try to start it with sudo rights? Bad idea, as it is a GUI application. You should never start GUI applications in sudo mode, unless there are really things you need to do as an admin with, which for Amarok is never the case. At least try installing debugging symbols and get a backtrace by other means, see also the link I gave you, you can always get a proper backtrace with gdb |