Sorry, but a debug output (pointless in this context) at the start of a report where bug description, reproducibility etc should be is not a good idea, it makes bug handling tiresome and unreadable.
In case of KDE applications it is always better to make a bug report upstream in https://bugs.kde.org This includes Amarok
Sorry, but a debug output (pointless in this context) at the start of a report where bug description, reproducibility etc should be is not a good idea, it makes bug handling tiresome and unreadable.
In case of KDE applications it is always better to make a bug report upstream in https:/ /bugs.kde. org This includes Amarok
Also please provide a full crash report, (not a debug output), with debug symbols enabled for Amarok and all its dependencies. See also https:/ /community. kde.org/ Guidelines_ and_HOWTOs/ Debugging/ How_to_ create_ useful_ crash_reports