Bug 316099 - ksysgurd crashes when clicking Tab Properties, when there are no tabs.
Summary: ksysgurd crashes when clicking Tab Properties, when there are no tabs.
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.10.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-04 06:25 UTC by Avihay
Modified: 2018-11-29 09:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Avihay 2013-03-04 06:25:47 UTC
Application: ksysguard (4.10.00)
KDE Platform Version: 4.10.00
Qt Version: 4.8.2
Operating System: Linux 3.2.0-38-generic i686
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I clicked Tab Properties, when there are no tabs.

All my tabs were corrupted by ksysgurd trying to save changes when the HDD is full, which allowed me to get to the rare state where I have no tabs open, and when I click the button...

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  WorkSheet::updateInterval (this=0x0) at ../../../ksysguard/gui/WorkSheet.cpp:751
#8  0x009f6842 in TopLevel::configureCurrentSheet (this=0x99e9f08) at ../../../ksysguard/gui/ksysguard.cpp:181
#9  0x009f86b0 in qt_static_metacall (_a=0xbfde58c8, _id=11, _o=0x99e9f08, _c=<optimized out>) at ./ksysguard.moc:85
#10 TopLevel::qt_static_metacall (_o=0x99e9f08, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbfde58c8) at ./ksysguard.moc:66
#11 0x01922bb1 in QMetaObject::activate (sender=0x9a035f0, m=0x4a4d3f8, local_signal_index=1, argv=0xbfde58c8) at kernel/qobject.cpp:3547
#12 0x040ce90d in QAction::triggered (this=0x9a035f0, _t1=false) at .moc/release-shared/moc_qaction.cpp:277
#13 0x040cebab in QAction::activate (this=0x9a035f0, event=QAction::Trigger) at kernel/qaction.cpp:1257
#14 0x045909d3 in QMenuPrivate::activateCausedStack (this=0x9916788, causedStack=..., action=0x9a035f0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1028
#15 0x045978af in QMenuPrivate::activateAction (this=0x9916788, action=0x9a035f0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1120
#16 0x0459a595 in QMenu::mouseReleaseEvent (this=0x9a16470, e=0xbfde6104) at widgets/qmenu.cpp:2360
#17 0x011cb0ec in KMenu::mouseReleaseEvent (this=0x9a16470, e=0xbfde6104) at ../../kdeui/widgets/kmenu.cpp:464
#18 0x0412fffc in QWidget::event (this=0x9a16470, event=0xbfde6104) at kernel/qwidget.cpp:8371
#19 0x0459901c in QMenu::event (this=0x9a16470, e=0xbfde6104) at widgets/qmenu.cpp:2469
#20 0x040d5df4 in notify_helper (e=0xbfde6104, receiver=0x9a16470, this=0x98bfcd8) at kernel/qapplication.cpp:4556
#21 QApplicationPrivate::notify_helper (this=0x98bfcd8, receiver=0x9a16470, e=0xbfde6104) at kernel/qapplication.cpp:4528
#22 0x040dbe74 in QApplication::notify (this=0x98bfcd8, receiver=0x9a16470, e=0xbfde6104) at kernel/qapplication.cpp:4099
#23 0x010ec9a1 in KApplication::notify (this=0x98b7c30, receiver=0x9a16470, event=0xbfde6104) at ../../kdeui/kernel/kapplication.cpp:311
#24 0x0190be0e in QCoreApplication::notifyInternal (this=0x98b7c30, receiver=0x9a16470, event=0xbfde6104) at kernel/qcoreapplication.cpp:915
#25 0x040d6db5 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#26 QApplicationPrivate::sendMouseEvent (receiver=0x9a16470, event=0xbfde6104, alienWidget=0x0, nativeWidget=0x9a16470, buttonDown=0x4a6acf4, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3167
#27 0x041636f2 in QETWidget::translateMouseEvent (this=0x9a16470, event=0xbfde65bc) at kernel/qapplication_x11.cpp:4551
#28 0x04161b2d in QApplication::x11ProcessEvent (this=0x98b7c30, event=0xbfde65bc) at kernel/qapplication_x11.cpp:3732
#29 0x0418ee1c in x11EventSourceDispatch (s=0x98cd3a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0x06219d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0x0621a125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#32 0x0621a201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0x0193ed87 in QEventDispatcherGlib::processEvents (this=0x98a37b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#34 0x0418ea1a in QGuiEventDispatcherGlib::processEvents (this=0x98a37b0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x0190a6ad in QEventLoop::processEvents (this=0xbfde68b4, flags=...) at kernel/qeventloop.cpp:149
#36 0x0190a949 in QEventLoop::exec (this=0xbfde68b4, flags=...) at kernel/qeventloop.cpp:204
#37 0x0191034a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#38 0x040d39c4 in QApplication::exec () at kernel/qapplication.cpp:3817
#39 0x009f8240 in kdemain (argc=1, argv=0xbfde6b14) at ../../../ksysguard/gui/ksysguard.cpp:581
#40 0x0804850b in main (argc=1, argv=0xbfde6b14) at ksysguard_dummy.cpp:3

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-29 22:35:27 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-13 14:41:55 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
mark the bug 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 3 Bug Janitor Service 2018-11-29 09:44:31 UTC
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!