| Summary: | Tried to enable scripts in Amarok and instantly crashed | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Bruce <bbrannock> |
| Component: | Tools/Script Manager | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | darthcodus |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 2.9.0 | ||
| Target Milestone: | kf5 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Bruce
2019-05-12 04:03:56 UTC
Thank you for your report. Unfortunately you do not have debugging symbols installed for Amarok and its dependencies, so your backtrace is of not much use. Please install those and provide a new backtrace. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports (In reply to Myriam Schweingruber from comment #1) > Thank you for your report. > Unfortunately you do not have debugging symbols installed for Amarok and its > dependencies, so your backtrace is of not much use. Please install those and > provide a new backtrace. > See also > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Hello, Myriam Schweingruber thank you for the response. I did get it fixed. What I did to make it crash was enable script console in settings which then in return created the crash. The quick fix to this is. Go to .kde/share/config/ and open amarokrc find Find EnableScriptConsole=true and edit it back to EnableScriptConsole=false That's the quick fix. Thank you for your reply! I will keep that in mind if I ever get a crash on a program to add debugging for that program. But I rarely get issues most of the time either in here or some Googling I can find the solution without submitting. This one frightened me because it's my favorite music player. Bruce However, if you would like me to replicate the crash with debugging symbols installed for Amarok. I would be more than happy to. What I saw when executing it in the terminal that it was a script that I think is broken or outdated causing the crash. I could be wrong though. no need to, it was most likely an outdated script, and there are open crash reports about the same already. (In reply to Myriam Schweingruber from comment #4) > no need to, it was most likely an outdated script, and there are open crash > reports about the same already. Ok thank you for your time |