Bug 244877 - System monitor crashed trying to monitor external temp sensor
Summary: System monitor crashed trying to monitor external temp sensor
Status: RESOLVED DUPLICATE of bug 227567
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-16 17:32 UTC by nate
Modified: 2010-10-11 14:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nate 2010-07-16 17:32:26 UTC
Application: ksysguard (4.4.5 (KDE 4.4.5))
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.33.6-147.fc13.i686.PAE i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Trying to connect to a remote box via SSH. Remote hardware sensor is as99127f. System monitor correctly lists all remote sensors, but crashes when I add any of the hardware temp sensors to the graphs. Remote system is a centos 5.6 i386 box. Local system is fedora core 13 i386.

The crash can be reproduced every time.

 -- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
[KCrash Handler]
#6  0x0624cea5 in unit (this=0x979d1f8, id=100, answerlist=...) at /usr/src/debug/kdebase-workspace-4.4.5/ksysguard/gui/ksgrd/SensorClient.h:191
#7  FancyPlotter::answerReceived (this=0x979d1f8, id=100, answerlist=...) at /usr/src/debug/kdebase-workspace-4.4.5/ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:684
#8  0x05a0af2a in KSGRD::SensorAgent::processAnswer (this=0x995ecb0, buf=0x99e0428 "0\nksysguardd> ", buflen=14) at /usr/src/debug/kdebase-workspace-4.4.5/ksysguard/gui/ksgrd/SensorAgent.cc:184
#9  0x05a13ecc in KSGRD::SensorShellAgent::msgRcvd (this=0x995ecb0) at /usr/src/debug/kdebase-workspace-4.4.5/ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#10 0x05a14cdf in KSGRD::SensorShellAgent::qt_metacall (this=0x995ecb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe2318c)
    at /usr/src/debug/kdebase-workspace-4.4.5/i686-redhat-linux-gnu/ksysguard/gui/ksgrd/SensorShellAgent.moc:78
#11 0x04159bcb in QMetaObject::metacall (object=0x995ecb0, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0xbfe2318c) at kernel/qmetaobject.cpp:237
#12 0x04168a75 in QMetaObject::activate (sender=0x995ec30, m=0x4268b68, local_signal_index=5, argv=0x0) at kernel/qobject.cpp:3295
#13 0x040f0b38 in QProcess::readyReadStandardOutput (this=0x995ec30) at .moc/release-shared/moc_qprocess.cpp:162
#14 0x040f5240 in QProcessPrivate::_q_canReadStandardOutput (this=0x96c6888) at io/qprocess.cpp:897
#15 0x040f56c6 in QProcess::qt_metacall (this=0x995ec30, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe23388) at .moc/release-shared/moc_qprocess.cpp:107
#16 0x044ca3db in KProcess::qt_metacall (this=0x995ec30, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbfe23388) at /usr/src/debug/kdelibs-4.4.5/i686-redhat-linux-gnu/kdecore/kprocess.moc:69
#17 0x04159bcb in QMetaObject::metacall (object=0x995ec30, cl=QMetaObject::InvokeMetaMethod, idx=17, argv=0xbfe23388) at kernel/qmetaobject.cpp:237
#18 0x04168a75 in QMetaObject::activate (sender=0x994bee8, m=0x426a9f0, local_signal_index=0, argv=0xbfe23388) at kernel/qobject.cpp:3295
#19 0x041b1794 in QSocketNotifier::activated (this=0x994bee8, _t1=20) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#20 0x0416e05f in QSocketNotifier::event (this=0x994bee8, e=0xbfe23814) at kernel/qsocketnotifier.cpp:317
#21 0x047b477c in QApplicationPrivate::notify_helper (this=0x935d2e0, receiver=0x994bee8, e=0xbfe23814) at kernel/qapplication.cpp:4306
#22 0x047bb1d6 in QApplication::notify (this=0x935d210, receiver=0x994bee8, e=0xbfe23814) at kernel/qapplication.cpp:3710
#23 0x052a300b in KApplication::notify (this=0x935d210, receiver=0x994bee8, event=0xbfe23814) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#24 0x04155133 in QCoreApplication::notifyInternal (this=0x935d210, receiver=0x994bee8, event=0xbfe23814) at kernel/qcoreapplication.cpp:726
#25 0x0417d81a in sendEvent (source=0x9360020) at kernel/qcoreapplication.h:215
#26 socketNotifierSourceDispatch (source=0x9360020) at kernel/qeventdispatcher_glib.cpp:110
#27 0x00aff525 in g_main_dispatch (context=0x935f690) at gmain.c:1960
#28 IA__g_main_context_dispatch (context=0x935f690) at gmain.c:2513
#29 0x00b03268 in g_main_context_iterate (context=0xa46490, block=1, dispatch=1, self=0x935d550) at gmain.c:2591
#30 0x00b03449 in IA__g_main_context_iteration (context=0x935f690, may_block=1) at gmain.c:2654
#31 0x0417d446 in QEventDispatcherGlib::processEvents (this=0x9347930, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#32 0x04863336 in QGuiEventDispatcherGlib::processEvents (this=0x9347930, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x0415380a in QEventLoop::processEvents (this=0xbfe23ab4, flags=...) at kernel/qeventloop.cpp:149
#34 0x04153b4a in QEventLoop::exec (this=0xbfe23ab4, flags=...) at kernel/qeventloop.cpp:201
#35 0x04157807 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#36 0x047b4828 in QApplication::exec () at kernel/qapplication.cpp:3585
#37 0x06281743 in kdemain (argc=1, argv=0xbfe23d44) at /usr/src/debug/kdebase-workspace-4.4.5/ksysguard/gui/ksysguard.cc:582
#38 0x0804871c in main (argc=1, argv=0xbfe23d44) at /usr/src/debug/kdebase-workspace-4.4.5/i686-redhat-linux-gnu/ksysguard/gui/ksysguard_dummy.cpp:3

This bug may be a duplicate of or related to bug 228916.

Possible duplicates by query: bug 228916.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-10-11 14:25:11 UTC

*** This bug has been marked as a duplicate of bug 227567 ***