Bug 230155 - system monitor crash when dragging a hd sensor into the sheet
Summary: system monitor crash when dragging a hd sensor into the sheet
Status: RESOLVED DUPLICATE of bug 223095
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-10 04:13 UTC by jensmh
Modified: 2010-07-12 14:46 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.83 KB, text/plain)
2010-04-16 06:15 UTC, akibukis
Details
New crash information added by DrKonqi (5.17 KB, text/plain)
2010-04-23 09:03 UTC, omega
Details
New crash information added by DrKonqi (5.13 KB, text/plain)
2010-04-26 01:50 UTC, chodge
Details
New crash information added by DrKonqi (6.12 KB, text/plain)
2010-05-10 14:25 UTC, grahamt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jensmh 2010-03-10 04:13:10 UTC
Application: ksysguard (4.4.1 (KDE 4.4.1))
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.33-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
The system monitor crashed when I dragged a disc sensor into the sheet.

 -- Backtrace:
Application: Systemmonitor (ksysguard), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  QColor (this=0x1720090, index=<value optimized out>) at /usr/include/qt4/QtGui/qcolor.h:289
#6  KSignalPlotter::beamColor (this=0x1720090, index=<value optimized out>) at ../../../../libs/ksysguard/signalplotter/ksignalplotter.cpp:118
#7  0x00007f49fa7553f7 in FancyPlotter::answerReceived (this=0x17202e0, id=<value optimized out>, answerlist=<value optimized out>) at ../../../ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:712
#8  0x00007f49f97e1d12 in KSGRD::SensorAgent::processAnswer (this=0x15d7cd0, buf=<value optimized out>, buflen=<value optimized out>) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#9  0x00007f49f97e93ee in KSGRD::SensorShellAgent::msgRcvd (this=0x15d7cd0) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#10 0x00007f49f97ea1d8 in KSGRD::SensorShellAgent::qt_metacall (this=0x15d7cd0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff653a5c70) at ./SensorShellAgent.moc:78
#11 0x00007f49f80adb1f in QMetaObject::activate (sender=0x15d12e0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffd) at kernel/qobject.cpp:3293
#12 0x00007f49f803abca in QProcessPrivate::_q_canReadStandardOutput (this=0x15ee0f0) at io/qprocess.cpp:887
#13 0x00007f49f803afa9 in QProcess::qt_metacall (this=0x15d12e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff653a5e70) at .moc/release-shared/moc_qprocess.cpp:107
#14 0x00007f49f871f748 in KProcess::qt_metacall (this=0x7fff653a5830, _c=24248464, _id=24, _a=0xfffffffd) at ./kprocess.moc:69
#15 0x00007f49f80adb1f in QMetaObject::activate (sender=0x1597ab0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffd) at kernel/qobject.cpp:3293
#16 0x00007f49f80f9a4e in QSocketNotifier::activated (this=0x7fff653a5830, _t1=15) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#17 0x00007f49f80b4ce3 in QSocketNotifier::event (this=0x1597ab0, e=0x7fff653a6520) at kernel/qsocketnotifier.cpp:317
#18 0x00007f49f74398fc in QApplicationPrivate::notify_helper (this=0x1414e00, receiver=0x1597ab0, e=0x7fff653a6520) at kernel/qapplication.cpp:4300
#19 0x00007f49f743fddb in QApplication::notify (this=0x1414d00, receiver=0x1597ab0, e=0x7fff653a6520) at kernel/qapplication.cpp:4183
#20 0x00007f49f8d02336 in KApplication::notify (this=0x1414d00, receiver=0x1597ab0, event=0x7fff653a6520) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x00007f49f809addc in QCoreApplication::notifyInternal (this=0x1414d00, receiver=0x1597ab0, event=0x7fff653a6520) at kernel/qcoreapplication.cpp:704
#22 0x00007f49f80c45ea in QCoreApplication::sendEvent (source=0x14179d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 socketNotifierSourceDispatch (source=0x14179d0) at kernel/qeventdispatcher_glib.cpp:110
#24 0x00007f49f1f5990e in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f49f1f5d2c8 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f49f1f5d3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f49f80c4233 in QEventDispatcherGlib::processEvents (this=0x13fd1a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#28 0x00007f49f74e932e in QGuiEventDispatcherGlib::processEvents (this=0x7fff653a5830, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f49f8099702 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007f49f8099adc in QEventLoop::exec (this=0x7fff653a6780, flags=) at kernel/qeventloop.cpp:201
#31 0x00007f49f809d81b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x00007f49fa7886c3 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../ksysguard/gui/ksysguard.cc:582
#33 0x00007f49fa3e4abd in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff653a6d08) at libc-start.c:222
#34 0x00000000004006b9 in _start ()

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

Possible duplicates by query: bug 229061, bug 223095, bug 213175.

Reported using DrKonqi
Comment 1 akibukis 2010-04-16 06:15:43 UTC
Created attachment 42813 [details]
New crash information added by DrKonqi

Same behaviour. Reproducible by dragging any of the sensors to graph.
Comment 2 omega 2010-04-23 09:03:44 UTC
Created attachment 42982 [details]
New crash information added by DrKonqi

crash step:

-open system monitor
-choose a sensor
-add sensor to a sheet
Comment 3 chodge 2010-04-26 01:50:07 UTC
Created attachment 43038 [details]
New crash information added by DrKonqi

Downloaded Simple Read Tab.  Added Sensor to graph and System Monitor crashed.
Comment 4 grahamt 2010-05-10 14:25:28 UTC
Created attachment 43430 [details]
New crash information added by DrKonqi

Kubuntu Lucid fresh install.
Hard Disk is continuously thrashing. Top shows kdeinit and firefox taking up no more than 20% CPU usage, but Ksysguard shows 100% cpu usage.
I wanted to show what process is using the HDD, and trying to do that using a HDD sensor crashes Ksysguard while dragging the sensor.
100% reproducable.
Comment 5 Nicolas L. 2010-07-12 14:46:57 UTC

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