Version: (using KDE KDE 3.5.5) Installed from: SuSE RPMs OS: Linux Thi is the backtrace: Controllo all'avvio della configurazione di sistema disattivato. (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) [Thread debugging using libthread_db enabled] [New Thread -1230870016 (LWP 4705)] (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) (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) [KCrash handler] #9 0xb618909f in KMiniPager::slotSetDesktop () from /opt/kde3/lib/kde3/minipager_panelapplet.so #10 0xb6189382 in KMiniPager::slotSetDesktopViewport () from /opt/kde3/lib/kde3/minipager_panelapplet.so #11 0xb6189ed5 in KMiniPager::qt_invoke () from /opt/kde3/lib/kde3/minipager_panelapplet.so #12 0xb75463cd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb7aa17a0 in KWinModule::currentDesktopViewportChanged () from /opt/kde3/lib/libkdecore.so.4 #14 0xb7aa6e9d in KWinModulePrivate::x11Event () from /opt/kde3/lib/libkdecore.so.4 #15 0xb7b6e623 in KApplication::x11EventFilter () from /opt/kde3/lib/libkdecore.so.4 #16 0xb7476c14 in qt_set_x11_event_filter () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0x08087760 in ?? () #18 0xbff515b8 in ?? () #19 0x00400000 in ?? () #20 0xb79b2ff4 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb79b2ff4 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0x080a7368 in ?? () #23 0xbff514c8 in ?? () #24 0xb7485a73 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb7485a73 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb749691a in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb74fe0e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb74fdf76 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #29 0xb74e700f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb6790232 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so #31 0xb7fa0514 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so #32 0x0804e33f in QGList::~QGList () #33 0x00000001 in ?? () #34 0x0807f990 in ?? () #35 0x00000001 in ?? () #36 0x00000000 in ?? ()
What about other information? What were you doing when the panel crashed? Are you able to reproduce that behaviour, and make it crash again? Does it still happen?
*** This bug has been marked as a duplicate of 139346 ***