Bug 229061 - ksysguard crashes after dragging a sensor on the harddisk sensor graph
Summary: ksysguard crashes after dragging a sensor on the harddisk sensor graph
Status: RESOLVED DUPLICATE of bug 223095
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-01 20:29 UTC by matthias sweertvaegher
Modified: 2010-07-12 14:46 UTC (History)
1 user (show)

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 matthias sweertvaegher 2010-03-01 20:29:42 UTC
Application: ksysguard (4.4.00 (KDE 4.4.0) "release 2")
KDE Platform Version: 4.4.00 (KDE 4.4.0) "release 2"
Qt Version: 4.6.2
Operating System: Linux 2.6.27.42-0.1-default x86_64
Distribution: "openSUSE 11.1 (x86_64)"

-- Information about the crash:
I just downloaded the harddisk information tab, but since i didn't get any output (although the io column in the table summoned from krunner did), I dragged one of the harddisk rate sensors in the display which caused it to crash. after I 've filed this report I will see if I can reproduce it always.

 -- Backtrace:
Application: System Monitor (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  KSignalPlotter::beamColor (this=0x996310, index=<value optimized out>) at /usr/include/QtGui/qcolor.h:289
#6  0x00007fbbee7aeec6 in FancyPlotter::answerReceived (this=0xbc77a0, id=<value optimized out>, answerlist=<value optimized out>)
    at /usr/src/debug/kdebase-workspace-4.4.0/ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:712
#7  0x00007fbbee029be5 in KSGRD::SensorAgent::processAnswer (this=0x780fe0, buf=<value optimized out>, buflen=<value optimized out>)
    at /usr/src/debug/kdebase-workspace-4.4.0/ksysguard/gui/ksgrd/SensorAgent.cc:184
#8  0x00007fbbee02a0b7 in KSGRD::SensorShellAgent::msgRcvd (this=0x780fe0) at /usr/src/debug/kdebase-workspace-4.4.0/ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#9  0x00007fbbee02a1c5 in KSGRD::SensorShellAgent::qt_metacall (this=0x780fe0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff04c4b860)
    at /usr/src/debug/kdebase-workspace-4.4.0/build/ksysguard/gui/ksgrd/SensorShellAgent.moc:78
#10 0x00007fbbfb78c627 in QMetaObject::activate (sender=0x7bd690, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x11b0c50) at kernel/qobject.cpp:3293
#11 0x00007fbbfb71543d in QProcessPrivate::_q_canReadStandardOutput (this=0x7966f0) at io/qprocess.cpp:887
#12 0x00007fbbfb7158b9 in QProcess::qt_metacall (this=0x7bd690, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff04c4ba30) at .moc/release-shared/moc_qprocess.cpp:107
#13 0x00007fbbfd3cc96d in KProcess::qt_metacall (this=0x7fff04c4b3d0, _c=10052368, _id=145, _a=0x11b0c50) at /usr/src/debug/kdelibs-4.4.0/build/kdecore/kprocess.moc:69
#14 0x00007fbbfb78c627 in QMetaObject::activate (sender=0x7dbaf0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x11b0c50) at kernel/qobject.cpp:3293
#15 0x00007fbbfb7da15e in QSocketNotifier::activated (this=0x7fff04c4b3d0, _t1=15) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#16 0x00007fbbfb793353 in QSocketNotifier::event (this=0x7dbaf0, e=0x7fff04c4c170) at kernel/qsocketnotifier.cpp:317
#17 0x00007fbbfa69968d in QApplicationPrivate::notify_helper (this=0x674f70, receiver=0x7dbaf0, e=0x7fff04c4c170) at kernel/qapplication.cpp:4300
#18 0x00007fbbfa6a0d94 in QApplication::notify (this=0x674e70, receiver=0x7dbaf0, e=0x7fff04c4c170) at kernel/qapplication.cpp:3704
#19 0x00007fbbfbec8a1b in KApplication::notify (this=0x674e70, receiver=0x7dbaf0, event=0x7fff04c4c170) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302
#20 0x00007fbbfb778c2c in QCoreApplication::notifyInternal (this=0x674e70, receiver=0x7dbaf0, event=0x7fff04c4c170) at kernel/qcoreapplication.cpp:704
#21 0x00007fbbfb7a3729 in socketNotifierSourceDispatch (source=0x678620) at kernel/qcoreapplication.h:215
#22 0x00007fbbf5ecf0fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fbbf5ed28cd in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fbbf5ed2a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fbbfb7a337c in QEventDispatcherGlib::processEvents (this=0x61bdd0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#26 0x00007fbbfa74c42f in QGuiEventDispatcherGlib::processEvents (this=0x7fff04c4b3d0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007fbbfb777502 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 80003984}) at kernel/qeventloop.cpp:149
#28 0x00007fbbfb7778dc in QEventLoop::exec (this=0x7fff04c4c3d0, flags={i = 80004064}) at kernel/qeventloop.cpp:201
#29 0x00007fbbfb779e06 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0x00007fbbee7b0c61 in kdemain (argc=1, argv=0x65e360) at /usr/src/debug/kdebase-workspace-4.4.0/ksysguard/gui/ksysguard.cc:582
#31 0x000000000040791d in launch (argc=1, _name=0x65e388 "/usr/bin/ksysguard", args=<value optimized out>, cwd=0x0, envc=1, envs=0x65e3af "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x65e3b8 "sushimonster;1267470639;641765;5058_TIME1327772") at /usr/src/debug/kdelibs-4.4.0/kinit/kinit.cpp:717
#32 0x0000000000408148 in handle_launcher_request (sock=9, who=<value optimized out>) at /usr/src/debug/kdelibs-4.4.0/kinit/kinit.cpp:1209
#33 0x00000000004086f5 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.4.0/kinit/kinit.cpp:1402
#34 0x00000000004092a6 in main (argc=4, argv=0x7fff04c4d738, envp=0x7fff04c4d760) at /usr/src/debug/kdelibs-4.4.0/kinit/kinit.cpp:1841

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

Possible duplicates by query: bug 225961, bug 223095, bug 213175, bug 212594.

Reported using DrKonqi
Comment 1 matthias sweertvaegher 2010-03-01 20:37:40 UTC
about reproducability:
it turns out doing the exact same actions, ksysguard does not always immediately crash. It does always crash eventually though.

Here is what I do:
1. import tab from file (the harddisk tab I downloaded and saved to disk)
2. drag the following sensor on the graph: Disk Throughput > sda_(8:0) > Rate > Read Data (float)

Sometimes it does not crash from the first time, but if I keep repeating the 2nd step, it does crash eventually.
Comment 2 Nicolas L. 2010-07-12 14:46:40 UTC

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