Summary: | amarok crashes randomly after pressing enter in playlist | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Victor Gavrish <loonyphoenix> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | nhn, teo |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Victor Gavrish
2010-03-10 18:50:32 UTC
I cannot reproduce this. Anyone else having any luck? If anyone manages to reproduce it, a backtrace with line numbers would be great! :-) which packages do I need debugging symbols for in case I encounter this crash again? Victor, please have a look here on how to get a valid backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports The debugging symbols recommended are those for Amarok, Phonon, kdelibs, libqt4 and libglib, this should cover most of the potential crashes. Mass closing NEEDSINFO bugs with no comment for at least 31 days. Dear reporter, thanks for your feedback. For efficient bug triaging we need not only one report but also constant feedback about the status of an issue, at least when we ask for it. If your request is still valid in our latest release in your opinion (2.3.1 beta 1) DO NOT REOPEN THIS BUG but file a fresh one instead. Developers need clean bug reports to be able to work efficiently. Provide at least a step-by-step guide on how to reproduce the issue, a backtrace in case of a crash and debug output if appropriate. And remember: * One issue per bug. Small, clean bug reports are best to work on. * Search for duplicates. Hint: we have useful categories for that. :) -> RESOLVED INVALID |