Bugzilla – Bug 155774
Kicker crashs when I restart suse 10.1
Last modified: 2006-03-13 09:49:26 UTC
Hello, I always get this when I restart my Labtop Toshiba SM30X-113. 1st log System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (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 -1230378144 (LWP 3606)] (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) [KCrash handler] #6 0xb70719b9 in malloc_consolidate () from /lib/libc.so.6 #7 0xb7072e34 in _int_free () from /lib/libc.so.6 #8 0xb7072f94 in free () from /lib/libc.so.6 #9 0xb755c0ab in QImage::freeBits () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb755e505 in QImage::reset () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb755ff7d in QImage::~QImage () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0xb621f690 in TaskBarContainer::windowListMenuAboutToHide () from /opt/kde3/lib/libtaskbar.so.1 #13 0xb703933d in exit () from /lib/libc.so.6 #14 0x0804e3a7 in ?? () #15 0x00000000 in ?? () Second log System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (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 -1231197344 (LWP 3484)] (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) [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb6f6e8b0 in raise () from /lib/libc.so.6 #8 0xb6f6ff83 in abort () from /lib/libc.so.6 #9 0xb6fa3f9b in __libc_message () from /lib/libc.so.6 #10 0xb6fa9921 in malloc_printerr () from /lib/libc.so.6 #11 0xb6faab80 in _int_free () from /lib/libc.so.6 #12 0xb6faaf94 in free () from /lib/libc.so.6 #13 0xb71186c1 in operator delete () from /usr/lib/libstdc++.so.6 #14 0xb6745827 in Kicker::~Kicker () from /opt/kde3/lib/libkdeinit_kicker.so #15 0xb675f7e4 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so #16 0xb7f06524 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so #17 0x0804e39f in ?? () #18 0x00000001 in ?? () #19 0x08072fa8 in ?? () #20 0x00000001 in ?? () #21 0x00000000 in ?? ()
The openSUSE product in Bugzilla is only for problems with the openSUSE wiki or with Bugzilla itself. Please reassign to correct product/component.
Please correct the component and version field first, then be more verbose about your problem. What are these backtraces and give detailed information about the used hardware (`hwinfo').
Hello, Please check https://bugzilla.novell.com/show_bug.cgi?id=155339 I already submitted the hwinfo there. Thank you, -Abdullah
Still, you gave no explicit information about the problem. Furthermore, please don't use cross-references to other reports, always attach the requested information to the report they were asked for.
Created attachment 72438 [details] back trace First log
Created attachment 72439 [details] second back trace
hopefully fixed for beta8, please test.