Bug 225961

Summary:	Crash with harddrive plugin
Product:	[Unmaintained] ksysguard	Reporter:	mathias.buren
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, mathias.buren
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mathias.buren 2010-02-08 22:24:23 UTC

Application that crashed: ksysguard
Version of the application: 4.3.4 (KDE 4.3.4)
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-bfs x86_64

What I was doing when the application crashed:
Dragging and dropping an item to the hdd sensors tab results in a crash, always reproducable.

 -- Backtrace:
Application: System Monitor (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f9c95c3e7d8 in KSignalPlotter::beamColor(int) () from /usr/lib/libkdeinit4_ksysguard.so
#6  0x00007f9c95c23d3d in FancyPlotter::answerReceived(int, QList<QByteArray> const&) () from /usr/lib/libkdeinit4_ksysguard.so
#7  0x00007f9c957a672b in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib/libksgrd.so.4
#8  0x00007f9c957ad51e in KSGRD::SensorShellAgent::msgRcvd() () from /usr/lib/libksgrd.so.4
#9  0x00007f9c957ae908 in KSGRD::SensorShellAgent::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libksgrd.so.4
#10 0x00007f9ca26a0bac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x00007f9ca262f935 in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007f9ca26329d9 in QProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x00007f9ca1f8b498 in KProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdecore.so.5
#14 0x00007f9ca26a0bac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#15 0x00007f9ca26d6ece in QSocketNotifier::activated(int) () from /usr/lib/libQtCore.so.4
#16 0x00007f9ca26a5543 in QSocketNotifier::event(QEvent*) () from /usr/lib/libQtCore.so.4
#17 0x00007f9ca04500dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00007f9ca04573be in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x00007f9ca1072146 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0x00007f9ca268ba7c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0x00007f9ca26b42ca in ?? () from /usr/lib/libQtCore.so.4
#22 0x00007f9c9f3ac26e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007f9c9f3afc28 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#24 0x00007f9c9f3afd50 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007f9ca26b3f73 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x00007f9ca04e32fe in ?? () from /usr/lib/libQtGui.so.4
#27 0x00007f9ca268a3b2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007f9ca268a784 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x00007f9ca268c939 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#30 0x00007f9c95c5b113 in kdemain () from /usr/lib/libkdeinit4_ksysguard.so
#31 0x00000000004069ae in _start ()

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

Reported using DrKonqi

Comment 1 Dario Andres 2010-02-10 13:46:05 UTC

This should be fixed on KDE SC 4.4. Merging with bug 213175. Regards

- Do you have any devices plugged in? E.g. mobile phone etc.
There's a related crash when you have a mount point with \n in its name.

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

Comment 2 mathias.buren 2010-02-10 17:38:59 UTC

I do not remember if I had any mountpoints with \n or spaces in them. However, I've upgraded to KDE 4.4 and it no longer crashes. It does not show all mount points, however:

It does not show the mountpoints for my lvm partitions:

/dev/mapper/lvmvolume-home on /home type ext3 (rw)
/dev/mapper/lvmvolume-var on /var type reiserfs (rw)

Only /boot which is /dev/sda3 with ext3. This bug can be closed, I'll see if there's already a bug report regarding lvm or not.

Comment 3 Dario Andres 2010-02-11 00:33:47 UTC

About the other bugs, please open a new report. 
Thanks