Bug 151425 - crash without obvious reasons
Summary: crash without obvious reasons
Status: RESOLVED DUPLICATE of bug 145566
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: Plasmoid / Applet (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-27 12:51 UTC by BORGULYA Gábor
Modified: 2008-01-16 18:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BORGULYA Gábor 2007-10-27 12:51:02 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

Kicker crashed without any obvious reasons, or activities to relate to. CPU meter had been quickly jumping from 0% to 100% and back before the crash - maybe unrelated.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233074496 (LWP 6253)]
(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]
#6  0xb604cead in FancyPlotterSettings::title ()
   from /usr/lib/kde3/sysguard_panelapplet.so
#7  0xb608391c in FancyPlotter::applySettings ()
   from /usr/lib/kde3/sysguard_panelapplet.so
#8  0xb6050a13 in FancyPlotter::qt_invoke ()
   from /usr/lib/kde3/sysguard_panelapplet.so
#9  0xb7220893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb7221338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6c0ed0c in KDialogBase::okClicked () from /usr/lib/libkdeui.so.4
#12 0xb6c0ed42 in KDialogBase::slotOk () from /usr/lib/libkdeui.so.4
#13 0xb6ceeab9 in KDialogBase::qt_invoke () from /usr/lib/libkdeui.so.4
#14 0xb6076753 in FancyPlotterSettings::qt_invoke ()
   from /usr/lib/kde3/sysguard_panelapplet.so
#15 0xb7220893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb7221338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb75b5907 in QButton::clicked () from /usr/lib/libqt-mt.so.3
#18 0xb72bef8c in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#19 0xb7257681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb71b7af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb71b9cae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb78bfca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb714a27d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#24 0xb7148ee2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#25 0xb7146fcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#26 0xb715e1a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0xb71d21ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0xb71d1fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0xb71b9699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0xb6640d92 in kdemain () from /usr/lib/libkdeinit_kicker.so
#31 0xb66b2454 in kdeinitmain () from /usr/lib/kde3/kicker.so
#32 0x0804e67f in ?? ()
#33 0x00000001 in ?? ()
#34 0x080a0758 in ?? ()
#35 0x00000001 in ?? ()
#36 0x00000000 in ?? ()
Comment 1 Greg Martyn 2008-01-16 18:45:52 UTC
It does look like that crash is related to ksysguard. Is it reproducable? If so, could you please install debugging symbols so that we can have a more meaningful crash report? To do so, run:
sudo apt-get install kdebase-dbg

Thanks.
Comment 2 Greg Martyn 2008-01-16 18:53:38 UTC
Nevermind.. looks like an existing bug.

*** This bug has been marked as a duplicate of 145566 ***
Comment 3 Greg Martyn 2008-01-16 18:57:51 UTC
If you can install the debugging symbols and reproduce this please report your results to bug #145566