Bug 227567

Summary: Adding new sensor "FailedDevices (integer)" as "Digital Number view" crashed the programm
Product: [Unmaintained] ksysguard Reporter: Harald Koschinski <harald>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: jelte, johnflux, nate, ralf.kistner
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Harald Koschinski 2010-02-18 20:36:18 UTC
Application that crashed: ksysguard
Version of the application: 4.3.1 (KDE 4.3.1) "release 6"
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Just adding some sensors 

 -- Backtrace:
Application: Systemmonitor (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f759be7591d in unit (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/ksgrd/SensorClient.h:152
#6  MultiMeter::answerReceived (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/SensorDisplayLib/MultiMeter.cc:101
#7  0x00007f759b9eb3bb in KSGRD::SensorAgent::processAnswer (this=0x81e6f0, buf=<value optimized out>, buflen=<value optimized out>)
    at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/ksgrd/SensorAgent.cc:184
#8  0x00007f759b9f21de in KSGRD::SensorShellAgent::msgRcvd (this=0x81e6f0) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#9  0x00007f759b9f35c8 in KSGRD::SensorShellAgent::qt_metacall (this=0x81e6f0, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd54135e0)
    at /usr/src/debug/kdebase-workspace-4.3.1/build/ksysguard/gui/ksgrd/SensorShellAgent.moc:72
#10 0x00007f75a651ffbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#11 0x00007f75a64aed75 in ?? () from /usr/lib64/libQtCore.so.4
#12 0x00007f75a64b1e19 in QProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00007f75a5e092a8 in KProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdecore.so.5
#14 0x00007f75a651ffbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#15 0x00007f75a655676e in QSocketNotifier::activated(int) () from /usr/lib64/libQtCore.so.4
#16 0x00007f75a6524953 in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x00007f75a42fb2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f75a430257e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f75a4ef58d6 in KApplication::notify (this=0x67d1f0, receiver=0x883c60, event=0x7fffd5413d20) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#20 0x00007f75a650addc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#21 0x00007f75a65336fa in ?? () from /usr/lib64/libQtCore.so.4
#22 0x00007f75a3244dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f75a32487b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f75a32488e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f75a65333a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f75a438e31e in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f75a6509712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f75a6509ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f75a650bc99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x00007f759be9f173 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/ksysguard.cc:579
#31 0x0000000000406f88 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=0x666f18 "pingu2;1266521234;546145;3360_TIME93695798") at /usr/src/debug/kdelibs-4.3.1/kinit/kinit.cpp:706
#32 0x0000000000407c80 in handle_launcher_request (sock=7, who=<value optimized out>) at /usr/src/debug/kdelibs-4.3.1/kinit/kinit.cpp:1198
#33 0x0000000000408131 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.3.1/kinit/kinit.cpp:1391
#34 0x0000000000408dfa in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/kdelibs-4.3.1/kinit/kinit.cpp:1830

This bug may be a duplicate of or related to bug 211069

Reported using DrKonqi
Comment 1 Christoph Feck 2010-10-11 14:25:11 UTC
*** Bug 244877 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2010-10-11 14:26:11 UTC
*** Bug 228916 has been marked as a duplicate of this bug. ***
Comment 3 Ralf Kistner 2010-11-10 23:20:16 UTC
Created attachment 53308 [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:

Followed the tutorial on
  http://techbase.kde.org/Development/Tutorials/Sensors

The sensor is detected correctly, but the app crashes when I try to add the sensor (any type of graph). Adding a custom sensor would be a very useful feature for me, but it seems to be completely undocumented and unstable at the moment.

-- Backtrace (Reduced):
#6  0x00007fb45366aa96 in unit (this=0x26760e0, id=100, answerlist=...) at ../../../ksysguard/gui/ksgrd/SensorClient.h:191
#7  FancyPlotter::answerReceived (this=0x26760e0, id=100, answerlist=...) at ../../../ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:684
#8  0x00007fb45278a74e in KSGRD::SensorAgent::processAnswer (this=0x26653d0, buf=<value optimized out>, buflen=<value optimized out>) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#9  0x00007fb4527921ae in KSGRD::SensorShellAgent::msgRcvd (this=0x26653d0) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#10 0x00007fb452792f98 in KSGRD::SensorShellAgent::qt_metacall (this=0x26653d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd038f110) at ./SensorShellAgent.moc:78
Comment 4 John Tapsell 2011-12-05 17:23:55 UTC
Probably fixed by:

commit f11be1b2a576db9b5e2defa9aacbf48e9cc5a00b
Author: John Tapsell <johnflux@gmail.com>
Date:   Fri Mar 18 15:07:51 2011 +0000

    Be a bit more relaxed about bad values from custom clients