Summary: | akregator crashed, no idea what I did | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Thorsten Zantis <bugs> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, bvv2001 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thorsten Zantis
2009-08-11 18:44:34 UTC
This looks related to bug 185597. Thanks BTW.. according to the backtrace you were doing some Tab-related action (may be closing one) *** This bug has been marked as a duplicate of bug 185597 *** my akregator crash too with this listing error This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4137700 (LWP 5860)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb565523c in nanosleep () from /lib/libc.so.6 [Current thread is 0 (process 5860)] Thread 1 (Thread 0xb4137700 (LWP 5860)): #0 0xb565523c in nanosleep () from /lib/libc.so.6 #1 0xb565505f in sleep () from /lib/libc.so.6 #2 0xb6af7ed8 in ?? () from /usr/lib/libkdeui.so.5 #3 0x00000000 in ?? () #0 0xb565523c in nanosleep () from /lib/libc.so.6 @Vadim Bazilevich: your crash could be completely different. We don't know as the information provided is incomplete. Please: 1) Updated to KDE SC 4.3.x. or 4.4.0 2) You probably need to install some special package to get a better backtrace (that depends on your distribution) 3) Create a new bug report for your crash Thanks |