Bug 186302

Summary: ksysguard crashes in nanosleep ()
Product: [Unmaintained] ksysguard Reporter: Beau V.C. Bellamy <bellamy.beau>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andresbajotierra, mail
Priority: NOR Keywords: triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Beau V.C. Bellamy 2009-03-06 03:41:53 UTC 
Version:           4.2.1 (using KDE 4.2.0)
Compiler:          gcc version 4.2.4 (Gentoo 4.2.4-r1 p1.1) CFLAGS="-O2 -march=athlon64 -pipe "
OS:                Linux
Installed from:    Gentoo Packages

Application: System Monitor (ksysguard), signal SIGSEGV
0x000000318fe98c01 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 30343)]

Thread 2 (Thread 0x40c0c950 (LWP 30404)):
#0  0x000000318febfca2 in select () from /lib/libc.so.6
#1  0x00007f8e373c7963 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f8e37318170 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x0000003190606067 in start_thread () from /lib/libpthread.so.0
#4  0x000000318fec5f6d in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8e3365a7b0 (LWP 30343)):
[KCrash Handler]
#5  0x00007f8e39cb34dc in FancyPlotter::timerTick () from /usr/kde/4.2/lib64/libkdeinit4_ksysguard.so
#6  0x00007f8e39ca56cf in KSGRD::SensorDisplay::qt_metacall () from /usr/kde/4.2/lib64/libkdeinit4_ksysguard.so
#7  0x00007f8e39cb23de in FancyPlotter::qt_metacall () from /usr/kde/4.2/lib64/libkdeinit4_ksysguard.so
#8  0x00007f8e373f121f in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f8e373efff5 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007f8e36a068ff in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007f8e36a0d335 in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#12 0x00007f8e381de8eb in KApplication::notify () from /usr/kde/4.2/lib64/libkdeui.so.5
#13 0x00007f8e373e1893 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007f8e37406726 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007f8e37407868 in QEventDispatcherUNIX::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007f8e36a80a96 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#17 0x00007f8e373e0c75 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007f8e373e0de6 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007f8e373e2d41 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007f8e39cef28c in kdemain () from /usr/kde/4.2/lib64/libkdeinit4_ksysguard.so
#21 0x000000318fe1e4a4 in __libc_start_main () from /lib/libc.so.6
#22 0x00000000004008a9 in _start ()
Comment 1 Dario Andres 2009-03-06 16:04:58 UTC 
This may be related to bug 179305
But, just to be sure: If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
Also, what were you doing when KSysguard crashed ?
Thanks :)
Comment 2 Julian Steinmann 2018-04-02 16:40:03 UTC 
The related bug has since been fixed. Can you still reproduce this crash with the newest version of KSysGuard? If not, I'll close this bug soon.
Comment 3 Andrew Crouthamel 2018-09-28 03:30:24 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-29 02:18:38 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!