Bug 263819 - System Monitor crashes upon dragging sensor from Sensor Browser onto Hard Disk Totals tab
Summary: System Monitor crashes upon dragging sensor from Sensor Browser onto Hard Dis...
Status: RESOLVED DUPLICATE of bug 223095
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-21 06:57 UTC by wearenotamused
Modified: 2012-10-28 21:53 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.82 KB, text/plain)
2011-01-23 22:52 UTC, d.stoynev
Details
New crash information added by DrKonqi (5.80 KB, text/plain)
2011-02-27 04:03 UTC, Boris Ribalkin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description wearenotamused 2011-01-21 06:57:56 UTC
Application: ksysguard (4.4.5 (KDE 4.4.5))
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-27-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Different things happen depending on the section of Sensor Browser under which the sensor being added is found.

Crashes:
System > Processors, Cores
CPU Load
Hardware Sensors
Partition Usage (some, sometimes)
Disk Throughput > sd*
Memory > swap
Network

Doesn't crash, doesn't add to graph:
logfiles
Partition Usage (some, sometimes)

Doesn't crash, adds to graph:
System > Uptime
Partition Usage > System Load
Disk Throughput > ram
Memory > physical
Process Count

What happens for a given item under Partition Usage varies. One that gets added one time can crash it the next. It seems like it might partially depend on the order in which multiple things are added.

The crash can be reproduced every time.

 -- Backtrace:
Application: System Monitor (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ff0a8c9c760 (LWP 13575))]

Thread 2 (Thread 0x7ff091422700 (LWP 13578)):
#0  0x00007ff0a5c88f93 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff0a264d4a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007ff0a264d8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007ff0a7291566 in QEventDispatcherGlib::processEvents (this=0xb991d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007ff0a7266992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007ff0a7266d6c in QEventLoop::exec (this=0x7ff091421db0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007ff0a7170d59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007ff0a7247178 in QInotifyFileSystemWatcherEngine::run (this=0xc58470) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007ff0a7173775 in QThreadPrivate::start (arg=0xc58470) at thread/qthread_unix.cpp:248
#9  0x00007ff0a6ee39ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007ff0a5c9570d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff0a8c9c760 (LWP 13575)):
[KCrash Handler]
#5  QColor (this=0x1079ef0, index=<value optimized out>) at /usr/include/qt4/QtGui/qcolor.h:289
#6  KSignalPlotter::beamColor (this=0x1079ef0, index=<value optimized out>) at ../../../../libs/ksysguard/signalplotter/ksignalplotter.cpp:118
#7  0x00007ff09aa893b7 in FancyPlotter::answerReceived (this=0x1079b60, id=<value optimized out>, answerlist=<value optimized out>) at ../../../ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:712
#8  0x00007ff09a335d52 in KSGRD::SensorAgent::processAnswer (this=0x979150, buf=<value optimized out>, buflen=<value optimized out>) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#9  0x00007ff09a33d42e in KSGRD::SensorShellAgent::msgRcvd (this=0x979150) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#10 0x00007ff09a33e218 in KSGRD::SensorShellAgent::qt_metacall (this=0x979150, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff2becee40) at ./SensorShellAgent.moc:78
#11 0x00007ff0a727ae3f in QMetaObject::activate (sender=0x979390, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffd) at kernel/qobject.cpp:3293
#12 0x00007ff0a720771a in QProcessPrivate::_q_canReadStandardOutput (this=0x978d00) at io/qprocess.cpp:887
#13 0x00007ff0a7207af9 in QProcess::qt_metacall (this=0x979390, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff2becf040) at .moc/release-shared/moc_qprocess.cpp:107
#14 0x00007ff0a8706a38 in KProcess::qt_metacall (this=0x7fff2becea00, _c=17276656, _id=10, _a=0xfffffffd) at ./kprocess.moc:69
#15 0x00007ff0a727ae3f in QMetaObject::activate (sender=0x979ec0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffd) at kernel/qobject.cpp:3293
#16 0x00007ff0a72c6c6e in QSocketNotifier::activated (this=0x7fff2becea00, _t1=14) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#17 0x00007ff0a7281fb3 in QSocketNotifier::event (this=0x979ec0, e=0x7fff2becf6f0) at kernel/qsocketnotifier.cpp:317
#18 0x00007ff0a640422c in QApplicationPrivate::notify_helper (this=0x7faa90, receiver=0x979ec0, e=0x7fff2becf6f0) at kernel/qapplication.cpp:4300
#19 0x00007ff0a640a6fb in QApplication::notify (this=0x7fa9f0, receiver=0x979ec0, e=0x7fff2becf6f0) at kernel/qapplication.cpp:4183
#20 0x00007ff0a77afa16 in KApplication::notify (this=0x7fa9f0, receiver=0x979ec0, event=0x7fff2becf6f0) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x00007ff0a726806c in QCoreApplication::notifyInternal (this=0x7fa9f0, receiver=0x979ec0, event=0x7fff2becf6f0) at kernel/qcoreapplication.cpp:704
#22 0x00007ff0a72918ca in QCoreApplication::sendEvent (source=0x7fe5d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 socketNotifierSourceDispatch (source=0x7fe5d0) at kernel/qeventdispatcher_glib.cpp:110
#24 0x00007ff0a26498c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007ff0a264d748 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007ff0a264d8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007ff0a7291513 in QEventDispatcherGlib::processEvents (this=0x76fda0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#28 0x00007ff0a64b446e in QGuiEventDispatcherGlib::processEvents (this=0x7fff2becea00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007ff0a7266992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007ff0a7266d6c in QEventLoop::exec (this=0x7fff2becf950, flags=) at kernel/qeventloop.cpp:201
#31 0x00007ff0a726aaab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x00007ff09aabc783 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../ksysguard/gui/ksysguard.cc:582
#33 0x00000000004070f3 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=1, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x7bcb88 "synapse;1295579770;718003;1808_TIME19451813") at ../../kinit/kinit.cpp:717
#34 0x0000000000407cb0 in handle_launcher_request (sock=8, who=<value optimized out>) at ../../kinit/kinit.cpp:1209
#35 0x000000000040823a in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1402
#36 0x0000000000408e22 in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1845

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

Possible duplicates by query: bug 263536, bug 238621, bug 238386, bug 230155, bug 229061.

Reported using DrKonqi
Comment 1 d.stoynev 2011-01-23 22:52:13 UTC
Created attachment 56364 [details]
New crash information added by DrKonqi

ksysguard (4.5.1 (KDE 4.5.1)) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

Well, the other guys have it said all. A crash when dragging and dropping a sensor over the Disk window.

-- Backtrace (Reduced):
#6  QColor (this=0x2ba6950, index=<value optimized out>) at /usr/include/qt4/QtGui/qcolor.h:292
#7  KSignalPlotter::beamColor (this=0x2ba6950, index=<value optimized out>) at ../../../../libs/ksysguard/signalplotter/ksignalplotter.cpp:109
#8  0x00007f46c3bbb3c7 in FancyPlotter::answerReceived (this=0x294a710, id=<value optimized out>, answerlist=<value optimized out>) at ../../../ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:712
#9  0x00007f46c2cda74e in KSGRD::SensorAgent::processAnswer (this=0x2423ae0, buf=<value optimized out>, buflen=<value optimized out>) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#10 0x00007f46c2ce21ae in KSGRD::SensorShellAgent::msgRcvd (this=0x2423ae0) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
Comment 2 Boris Ribalkin 2011-02-27 04:03:00 UTC
Created attachment 57545 [details]
New crash information added by DrKonqi

ksysguard (4.6.00 (4.6.0)) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0

- What I was doing when the application crashed:

Tried to drag CPU sensors to the graph.

- Custom settings of the application:

Installed Hard Disk Tab

-- Backtrace (Reduced):
#6  QColor (this=0x1473a40, index=<value optimized out>) at /usr/include/qt4/QtGui/qcolor.h:292
#7  KSignalPlotter::beamColor (this=0x1473a40, index=<value optimized out>) at ../../../../libs/ksysguard/signalplotter/ksignalplotter.cpp:109
#8  0x00007f89faf91317 in FancyPlotter::answerReceived (this=0x12d8210, id=<value optimized out>, answerlist=<value optimized out>) at ../../../ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:712
#9  0x00007f89fa09774e in KSGRD::SensorAgent::processAnswer (this=0xdf81a0, buf=<value optimized out>, buflen=<value optimized out>) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#10 0x00007f89fa09f1ae in KSGRD::SensorShellAgent::msgRcvd (this=0xdf81a0) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
Comment 3 Dario Andres 2011-03-08 19:51:19 UTC
[Comment from a bug triager]
This issue is being tracked at bug 223095.
Merging. Thanks

*** This bug has been marked as a duplicate of bug 223095 ***
Comment 4 Aleix Pol 2012-10-28 21:33:43 UTC
Git commit fb353eee24d0e034a03f73fcc3656012483fd3c1 by Aleix Pol.
Committed on 28/10/2012 at 19:49.
Pushed by apol into branch 'master'.

Make configure dialog option more persistant

When we save the configure project dialog, also save the last used
install prefix for next runs.

M  +1    -0    projectmanagers/cmake/settings/cmakepreferences.cpp

http://commits.kde.org/kdevelop/fb353eee24d0e034a03f73fcc3656012483fd3c1
Comment 5 Christoph Feck 2012-10-28 21:52:51 UTC
Aleix, wrong bug number :) Please check, which bug you wanted to close. Also, please use FIXED-IN: tags in commits (4.9.3 or 4.10).
Comment 6 Christoph Feck 2012-10-28 21:53:53 UTC

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