Application that crashed: ksysguard Version of the application: 4.3.1 (KDE 4.3.1) "release 163" KDE Version: 4.3.1 (KDE 4.3.1) "release 163" Qt Version: 4.5.2 Operating System: Linux 2.6.27.29-0.1-default x86_64 Distribution: "openSUSE 11.1 (x86_64)" What I was doing when the application crashed: ksysguard crashes when closing properties windows of network history plot with ok or apply. Could be a duplicat of bug 203382, which says it is fixed, but I'm using KDE 4.3.1 "release 163" and ksysguard is still crahing. -- Backtrace: Application: Systemmonitor (ksysguard), signal: Segmentation fault [KCrash Handler] #4 SensorModelEntry::color (this=0x1e1) at /usr/include/QtGui/qcolor.h:259 #5 0x00007fdc188efdf5 in FancyPlotter::applySettings (this=0x7cf090) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:260 #6 0x00007fdc188f0e2d in FancyPlotter::qt_metacall (this=0x7cf090, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.1/build/ksysguard/gui/FancyPlotter.moc:75 #7 0x00007fdc15f6f6e2 in QMetaObject::activate (sender=0x7c5770, from_signal_index=<value optimized out>, to_signal_index=43, argv=0x2) at kernel/qobject.cpp:3113 #8 0x00007fdc16d0ec35 in KDialog::slotButtonClicked(int) () from /usr/lib64/libkdeui.so.5 #9 0x00007fdc16d10e6d in KDialog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5 #10 0x00007fdc16dc69a6 in KPageDialog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5 #11 0x00007fdc188f25a5 in FancyPlotterSettings::qt_metacall (this=0x7ffffecbbe80, _c=481, _id=8295584, _a=0x2) at /usr/src/debug/kdebase-workspace-4.3.1/build/ksysguard/gui/FancyPlotterSettings.moc:68 #12 0x00007fdc15f6f6e2 in QMetaObject::activate (sender=0x741238, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x2) at kernel/qobject.cpp:3113 #13 0x00007fdc15f72ece in QSignalMapper::mapped (this=0x7ffffecbbe80, _t1=8) at .moc/release-shared/moc_qsignalmapper.cpp:95 #14 0x00007fdc15f73770 in QSignalMapper::map (this=0x741238, sender=0x816060) at kernel/qsignalmapper.cpp:266 #15 0x00007fdc15f743a0 in QSignalMapper::qt_metacall (this=0x741238, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffffecbc380) at .moc/release-shared/moc_qsignalmapper.cpp:81 #16 0x00007fdc15f6f6e2 in QMetaObject::activate (sender=0x816060, from_signal_index=<value optimized out>, to_signal_index=30, argv=0x2) at kernel/qobject.cpp:3113 #17 0x00007fdc157e3b37 in QAbstractButton::clicked (this=0x7ffffecbbe80, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #18 0x00007fdc1553de7b in QAbstractButtonPrivate::emitClicked (this=0x805930) at widgets/qabstractbutton.cpp:543 #19 0x00007fdc1553faa2 in QAbstractButtonPrivate::click (this=0x805930) at widgets/qabstractbutton.cpp:536 #20 0x00007fdc1553fcf5 in QAbstractButton::mouseReleaseEvent (this=0x816060, e=0x7ffffecbcb50) at widgets/qabstractbutton.cpp:1115 #21 0x00007fdc15230a9d in QWidget::event (this=0x816060, event=0x7ffffecbcb50) at kernel/qwidget.cpp:7549 #22 0x00007fdc151dfabd in QApplicationPrivate::notify_helper (this=0x623560, receiver=0x816060, e=0x7ffffecbcb50) at kernel/qapplication.cpp:4056 #23 0x00007fdc151e84aa in QApplication::notify (this=<value optimized out>, receiver=0x816060, e=0x7ffffecbcb50) at kernel/qapplication.cpp:3758 #24 0x00007fdc16d9b02b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #25 0x00007fdc15f5a94c in QCoreApplication::notifyInternal (this=0x623490, receiver=0x816060, event=0x7ffffecbcb50) at kernel/qcoreapplication.cpp:610 #26 0x00007fdc151e76f8 in QApplicationPrivate::sendMouseEvent (receiver=0x816060, event=0x7ffffecbcb50, alienWidget=0x816060, nativeWidget=0x7c5770, buttonDown=<value optimized out>, lastMouseReceiver=@0x7fdc15bf2f30) at ../../src/corelib/kernel/qcoreapplication.h:216 #27 0x00007fdc152514c9 in QETWidget::translateMouseEvent (this=0x7c5770, event=<value optimized out>) at kernel/qapplication_x11.cpp:4402 #28 0x00007fdc15250535 in QApplication::x11ProcessEvent (this=0x623490, event=0x7ffffecbe6d0) at kernel/qapplication_x11.cpp:3543 #29 0x00007fdc15277824 in x11EventSourceDispatch (s=0x626df0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #30 0x00007fdc0fd720fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #31 0x00007fdc0fd758cd in ?? () from /usr/lib64/libglib-2.0.so.0 #32 0x00007fdc0fd75a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #33 0x00007fdc15f83d3f in QEventDispatcherGlib::processEvents (this=0x60a1a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #34 0x00007fdc15276faf in QGuiEventDispatcherGlib::processEvents (this=0x7ffffecbbe80, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #35 0x00007fdc15f591d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -20190784}) at kernel/qeventloop.cpp:149 #36 0x00007fdc15f595a4 in QEventLoop::exec (this=0x7ffffecbea00, flags={i = -20190704}) at kernel/qeventloop.cpp:201 #37 0x00007fdc15f5b894 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #38 0x00007fdc189282a4 in kdemain (argc=1, argv=0x7ffffecbef88) at /usr/src/debug/kdebase-workspace-4.3.1/ksysguard/gui/ksysguard.cc:579 #39 0x00007fdc1458c586 in __libc_start_main () from /lib64/libc.so.6 #40 0x00000000004007a9 in _start () at ../sysdeps/x86_64/elf/start.S:113 This bug may be a duplicate of or related to bug 203382 Reported using DrKonqi
*** Bug 206196 has been marked as a duplicate of this bug. ***
*** Bug 206640 has been marked as a duplicate of this bug. ***
Created attachment 36824 [details] my bt of the crash I can confirm this with 4.3.1 on Fedora 11. It is sufficient to open the settings menu of "Network History" and just click "Apply" without changing any settings.
I can confirm this Bug with openSUSE 11.2 Milestone 7 and Kubuntu 9.10 Alpha 5. cpu and memory graph scale are unaffected, it happend only in the network properties.
I can confirm this bug on Gentoo, KDE 4.3.1, Qt 4.5.2. Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault [KCrash Handler] #5 SensorModelEntry::color (this=0x1e1) at /usr/include/qt4/QtGui/qcolor.h:259 #6 0x00007f4534b0c5da in FancyPlotter::applySettings (this=0x941100) at /var/tmp/portage/kde-base/ksysguard-4.3.1/work/ksysguard-4.3.1/ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:260 #7 0x00007f4534b0d59c in FancyPlotter::qt_metacall (this=0x941100, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=<value optimized out>) at /var/tmp/portage/kde-base/ksysguard-4.3.1/work/ksysguard-4.3.1_build/ksysguard/gui/FancyPlotter.moc:75 #8 0x00007f4532266cd0 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f4532fbd317 in KDialog::slotButtonClicked () from /usr/lib64/libkdeui.so.5 #10 0x00007f4532fbf095 in KDialog::qt_metacall () from /usr/lib64/libkdeui.so.5 #11 0x00007f4533067e7e in KPageDialog::qt_metacall () from /usr/lib64/libkdeui.so.5 #12 0x00007f4534b0e9cf in FancyPlotterSettings::qt_metacall (this=0x7fffb7acb190, _c=481, _id=10817744, _a=0x2) at /var/tmp/portage/kde-base/ksysguard-4.3.1/work/ksysguard-4.3.1_build/ksysguard/gui/FancyPlotterSettings.moc:68 #13 0x00007f4532266cd0 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #14 0x00007f453226ac90 in QSignalMapper::mapped () from /usr/lib64/qt4/libQtCore.so.4 #15 0x00007f453226ad1a in QSignalMapper::map () from /usr/lib64/qt4/libQtCore.so.4 #16 0x00007f453226bd02 in QSignalMapper::qt_metacall () from /usr/lib64/qt4/libQtCore.so.4 #17 0x00007f4532266cd0 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #18 0x00007f4531b6d2eb in QAbstractButton::clicked () from /usr/lib64/qt4/libQtGui.so.4 #19 0x00007f453193fe40 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #20 0x00007f4531940b8a in ?? () from /usr/lib64/qt4/libQtGui.so.4 #21 0x00007f4531940d3f in QAbstractButton::mouseReleaseEvent () from /usr/lib64/qt4/libQtGui.so.4 #22 0x00007f45316a7cd0 in QWidget::event () from /usr/lib64/qt4/libQtGui.so.4 #23 0x00007f4531663525 in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #24 0x00007f453166afe8 in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #25 0x00007f453303f7a4 in KApplication::notify () from /usr/lib64/libkdeui.so.5 #26 0x00007f4532256a0e in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #27 0x00007f453166a306 in QApplicationPrivate::sendMouseEvent () from /usr/lib64/qt4/libQtGui.so.4 #28 0x00007f45316bc364 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #29 0x00007f45316baef8 in QApplication::x11ProcessEvent () from /usr/lib64/qt4/libQtGui.so.4 #30 0x00007f45316dd88b in ?? () from /usr/lib64/qt4/libQtGui.so.4 #31 0x00007f452c1f3086 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0x00007f452c1f5ffd in ?? () from /usr/lib/libglib-2.0.so.0 #33 0x00007f452c1f6193 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0x00007f4532278049 in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #35 0x00007f45316dd1f6 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #36 0x00007f4532255764 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #37 0x00007f45322558ef in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #38 0x00007f4532257484 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #39 0x00007f4534b4161a in kdemain (argc=1, argv=0x7fffb7ace298) at /var/tmp/portage/kde-base/ksysguard-4.3.1/work/ksysguard-4.3.1/ksysguard/gui/ksysguard.cc:579 #40 0x00007f45309f55c6 in __libc_start_main () from /lib/libc.so.6 #41 0x00000000004008a9 in _start ()
*** Bug 207545 has been marked as a duplicate of this bug. ***
The PLD-Linux KDE 4.3.1 LiveCD is not affected! PLD-Linux runs with NetworkManager Applet 0.7.1, perhaps the KNetworkManager is the problem? openSUSE 11.2 Milestone 7 and Kubuntu 9.10 Alpha 5 which are affected, runs with KNetworkManager.
Created attachment 37330 [details] I can confirm this with 4.3.1 on Arch
Confirmed here as well on Gentoo, KDE 4.3.1, Qt 4.5.2. Crash after attempting to change horizontal scale of network graph to 1 pixel per time period. Application: System Monitor (kdeinit4), signal: Segmentation fault [KCrash Handler] #5 0x00007f65cb34fd90 in SensorModelEntry::color () from /usr/lib64/libkdeinit4_ksysguard.so #6 0x00007f65cb33740d in FancyPlotter::applySettings () from /usr/lib64/libkdeinit4_ksysguard.so #7 0x00007f65cb33841d in FancyPlotter::qt_metacall () from /usr/lib64/libkdeinit4_ksysguard.so #8 0x00007f65d66d6fd5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007f65d502c325 in KDialog::slotButtonClicked () from /usr/lib64/libkdeui.so.5 #10 0x00007f65d502e50d in KDialog::qt_metacall () from /usr/lib64/libkdeui.so.5 #11 0x00007f65d50e27e6 in KPageDialog::qt_metacall () from /usr/lib64/libkdeui.so.5 #12 0x00007f65cb339b55 in FancyPlotterSettings::qt_metacall () from /usr/lib64/libkdeinit4_ksysguard.so #13 0x00007f65d66d6fd5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #14 0x00007f65d66db11e in QSignalMapper::mapped () from /usr/lib64/qt4/libQtCore.so.4 #15 0x00007f65d66db1c0 in QSignalMapper::map () from /usr/lib64/qt4/libQtCore.so.4 #16 0x00007f65d66dc398 in QSignalMapper::qt_metacall () from /usr/lib64/qt4/libQtCore.so.4 #17 0x00007f65d66d6fd5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #18 0x00007f65d4af7757 in QAbstractButton::clicked (this=0x7fff95595140, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #19 0x00007f65d489416b in QAbstractButtonPrivate::emitClicked (this=0x2857c10) at widgets/qabstractbutton.cpp:543 #20 0x00007f65d4895012 in QAbstractButtonPrivate::click (this=0x2857c10) at widgets/qabstractbutton.cpp:536 #21 0x00007f65d4895245 in QAbstractButton::mouseReleaseEvent (this=0x244dfa0, e=0x7fff95596020) at widgets/qabstractbutton.cpp:1115 #22 0x00007f65d45d5b20 in QWidget::event (this=0x244dfa0, event=0x7fff95596020) at kernel/qwidget.cpp:7549 #23 0x00007f65d4588c3d in QApplicationPrivate::notify_helper (this=0x23749d0, receiver=0x244dfa0, e=0x7fff95596020) at kernel/qapplication.cpp:4056 #24 0x00007f65d4590cd3 in QApplication::notify (this=<value optimized out>, receiver=0x244dfa0, e=0x7fff95596020) at kernel/qapplication.cpp:3758 #25 0x00007f65d50b740b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #26 0x00007f65d66c5123 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #27 0x00007f65d45921a8 in QApplicationPrivate::sendMouseEvent (receiver=0x244dfa0, event=0x7fff95596020, alienWidget=0x244dfa0, nativeWidget=0x244f640, buttonDown=<value optimized out>, lastMouseReceiver=@0x7f65d4e98ef0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #28 0x00007f65d45eb3cc in QETWidget::translateMouseEvent (this=0x244f640, event=<value optimized out>) at kernel/qapplication_x11.cpp:4404 #29 0x00007f65d45e9ee5 in QApplication::x11ProcessEvent (this=0x23748d0, event=0x7fff95597a10) at kernel/qapplication_x11.cpp:3545 #30 0x00007f65d460e644 in x11EventSourceDispatch (s=0x23786c0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #31 0x00007f65d34bd7d1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0x00007f65d34c0e88 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #33 0x00007f65d34c104c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0x00007f65d66e9d0f in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #35 0x00007f65d460df0f in QGuiEventDispatcherGlib::processEvents (this=0x7fff95595140, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #36 0x00007f65d66c3b22 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #37 0x00007f65d66c3cbc in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #38 0x00007f65d66c5c94 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #39 0x00007f65cb36f254 in kdemain () from /usr/lib64/libkdeinit4_ksysguard.so #40 0x0000000000407514 in launch () #41 0x0000000000407d00 in handle_launcher_request () #42 0x000000000040825e in handle_requests () #43 0x0000000000408d7d in main ()
*** Bug 209952 has been marked as a duplicate of this bug. ***
Created attachment 37514 [details] SystemLoad2.sgrd this one works, it is different from the /usr/share/kde4/apps/ksysguard/SystemLoad2.sgrd
I have found a workaround that may point to a cause: Editing the ~/.kde/share/apps/ksysguard/SystemLoad2.sgrd in a text editor allows me to change the parameters of the network history graph. The ksysguard program accepts the changes w/o problems. Qt: 4.5.3 KDE: 4.3.2 (KDE 4.3.2) System Monitor: 4.3.2 (KDE 4.3.2-1)unstable 2.6.31-3.slh.1-sidux-686 I can edit the "SystemLoad2.sgrd" but ksysguard itself cannot?
*** Bug 211228 has been marked as a duplicate of this bug. ***
*** Bug 212859 has been marked as a duplicate of this bug. ***
*** Bug 213892 has been marked as a duplicate of this bug. ***
Just wondering if it might be related to 4.3.1. Does it also occur when the 4.3.2 version of ksysguard is tested?
*** Bug 213577 has been marked as a duplicate of this bug. ***
*** Bug 213776 has been marked as a duplicate of this bug. ***
(In reply to comment #16) > Just wondering if it might be related to 4.3.1. Does it also occur when the > 4.3.2 version of ksysguard is tested? It still happens to me with 4.3.3 and it seems to happen with 4.3.2 also according to comment #17/Bug 213577.
> It still happens to me with 4.3.3 and it seems to happen with 4.3.2 also > according to comment #17/Bug 213577. Right, the bug fix was never backported to the 4.3 branch (lack of manpower).
*** Bug 213488 has been marked as a duplicate of this bug. ***
@John: should this bug report be closed? (if it is fixed in trunk)
When can the fix reach end users (ie. update repo or something)?
> When can the fix reach end users (ie. update repo or something)? I think KDE 4.4 will be released end of this year. In the case of Ubuntu, it would thus be in the next release in April 2010. Dunno about other distros.
Users of Kubuntu backports will be able to get it as soon as its available, but not in the regular repositories. (Sorry if this email-response is not meant for reply comments=( ) Kevin On Wed, Nov 11, 2009 at 4:52 AM, John Tapsell <johnflux@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=206125 > > > > > > --- Comment #24 from John Tapsell <johnflux gmail com> 2009-11-11 13:52:45 > --- > > When can the fix reach end users (ie. update repo or something)? > I think KDE 4.4 will be released end of this year. In the case of > Ubuntu, it would thus be in the next release in April 2010. Dunno > about other distros. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. >
*** Bug 216190 has been marked as a duplicate of this bug. ***
*** Bug 216294 has been marked as a duplicate of this bug. ***
@John: should this bug report be closed ? Regards
Yep - closing as it should be fixed in 4.4
*** Bug 217320 has been marked as a duplicate of this bug. ***
*** Bug 217121 has been marked as a duplicate of this bug. ***
*** Bug 216559 has been marked as a duplicate of this bug. ***
*** Bug 220028 has been marked as a duplicate of this bug. ***
*** Bug 232242 has been marked as a duplicate of this bug. ***
*** Bug 233227 has been marked as a duplicate of this bug. ***