| Summary: | Amarok crashed when I exited | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | daramas444 |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED BACKTRACE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 2.5.0 | ||
| Target Milestone: | 2.6 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
output console amarok
output console amarok --debug |
||
|
Description
daramas444
2012-06-08 22:04:53 UTC
Could you please install the debugging symbols for Amarok and provide a better backtrace? ok I'm on it Created attachment 71813 [details]
output console amarok
Created attachment 71814 [details]
output console amarok --debug
okayyyyyyyy I don't know wtf is happening but when I upload an attachment, it sends the file without comments... anyway SO once again. amarok-debuginfo is already installed, as long as qt-debuginfo and kdelibs-debuginfo I tried to open Amarok, play a song then exit it. worked like a charm. then tried again. wouldn't open. so I open it via terminal to have more info, cf file output console amarok. Then I typed amarok --debug ; output starting from the "exit" order is in the file output console amarok --debug Hope that'll help. PLease let me know if I can do anything else Thank you for all that information, but I don't need the console output, I need the backtrace for the crash you reported :) Since it doesn't show a crash related to Amarok but a lot of ?? lines I assumed you didn't have the debuginfo for it. The crash is most likely due to another part in your system, but the backtrace is not useful, see the last few lines: #21 0x00000037fd2b8a60 in QRegExp::~QRegExp (this=0x37fe8e3df8, __in_chrg=<optimized out>) at tools/qregexp.cpp:3835 #22 0x00000034a5039d4d in __cxa_finalize (d=0x37fe8cbc80) at cxa_finalize.c:56 #23 0x00000037fe4a4b56 in __do_global_dtors_aux () from /usr/lib64/libkdecore.so.5 #24 0x00007fff62fd4e10 in ?? () #25 0x00007fff62fd5610 in ?? () #26 0x00000037fe64cda1 in _fini () from /usr/lib64/libkdecore.so.5 #27 0x00007fff62fd5610 in ?? () #28 0x00000034a4c0f79d in _dl_fini () at dl-fini.c:249 Backtrace stopped: previous frame inner to this frame (corrupt stack?) oh ok I see. So I assume there is no point to try to generate a proper backtrace using gdb ? (In reply to comment #7) > oh ok I see. So I assume there is no point to try to generate a proper > backtrace using gdb ? There always is, just make sure you have all necessary debugging symbols installed for kdelibs, kde-runtime, amarok, phonon and its backends. In general, having debugging symbols for all dependencies is a good idea, especially when the previous backtrace is non-conclusive. Hi Myriam, Sorry for the delay. I can't reproduce the bug, it looks like an update (kernel or amarok or whatever...) has solved the problem. Thanks for your time ! |