Summary: | Amarok crashes after start version: 2.2.2-4 | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Janík Tománek <janiktomanek> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 2.2.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Janík Tománek
2010-02-11 18:52:31 UTC
Sorry, but your backtrace is not useful, as you are lacking debugging symbols. Please check here on how to get a valid backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports FWIW, your backtrace seems to indicate a problem with either the Script Manager or a 3rd-party script. This might well be a duplicate of bug 219441 (In reply to comment #1) > Sorry, but your backtrace is not useful, as you are lacking debugging symbols. > Please check here on how to get a valid backtrace: > > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > > FWIW, your backtrace seems to indicate a problem with either the Script Manager > or a 3rd-party script. This might well be a duplicate of bug 219441 I've looked on the Archlinux wiki and for creating more useful crash report I would need to recompile these packages, but I am sorry, I don't want to do it. But this situation can change soon, with some debug support in Arch. I will try to delete .amarok directory Closing as duplicate of bug 219441 then *** This bug has been marked as a duplicate of bug 219441 *** |