Bug 199032 - System monitor crashed while trying to configure the colours of a graph
Summary: System monitor crashed while trying to configure the colours of a graph
Status: RESOLVED DUPLICATE of bug 179305
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-05 16:45 UTC by Sputnik
Modified: 2009-07-05 18:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sputnik 2009-07-05 16:45:31 UTC
Application that crashed: ksysguard
Version of the application: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-13-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Systemmonitor (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  SensorModelEntry::color (this=0x63630000) at /usr/include/qt4/QtGui/qcolor.h:259
#7  0xb4b05908 in FancyPlotter::applySettings (this=0x8fefc28) at /build/buildd/kdebase-workspace-4.2.95/ksysguard/gui/SensorDisplayLib/FancyPlotter.cc:260
#8  0xb4b06953 in FancyPlotter::qt_metacall (this=0x8fefc28, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf80af48)
    at /build/buildd/kdebase-workspace-4.2.95/obj-i486-linux-gnu/ksysguard/gui/FancyPlotter.moc:75
#9  0xb7ee5ca8 in QMetaObject::activate (sender=0x94f2c50, from_signal_index=45, to_signal_index=45, argv=0x0) at kernel/qobject.cpp:194
#10 0xb7ee6932 in ~QObject (this=0x94f2c50) at ../../include/QtCore/../../src/corelib/tools/qlist.h:119
#11 0xb7400217 in KDialog::okClicked (this=0x94f2c50) at /build/buildd/kde4libs-4.2.95/obj-i486-linux-gnu/kdeui/kdialog.moc:252
#12 0xb7402a58 in KDialog::slotButtonClicked (this=0x4, button=-1218121740) at /build/buildd/kde4libs-4.2.95/kdeui/dialogs/kdialog.cpp:854
#13 0xb7404c6c in KDialog::qt_metacall (this=0x94f2c50, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbf80b13c) at /build/buildd/kde4libs-4.2.95/obj-i486-linux-gnu/kdeui/kdialog.moc:184
#14 0xb74cb3aa in KPageDialog::qt_metacall (this=0x94f2c50, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbf80b13c) at /build/buildd/kde4libs-4.2.95/obj-i486-linux-gnu/kdeui/kpagedialog.moc:64
#15 0xb4b0877a in FancyPlotterSettings::qt_metacall (this=0x94f2c50, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbf80b13c)
    at /build/buildd/kdebase-workspace-4.2.95/obj-i486-linux-gnu/ksysguard/gui/FancyPlotterSettings.moc:68
#16 0xb7ee5ca8 in QMetaObject::activate (sender=0x8ffb020, from_signal_index=4, to_signal_index=4, argv=0xbf80b13c) at kernel/qobject.cpp:194
#17 0xb7ee6932 in ~QObject (this=0x8ffb020) at ../../include/QtCore/../../src/corelib/tools/qlist.h:119
#18 0xb7ee8be3 in QSignalMapper::mapping (this=0x8ffb020, id=@0x4) at ../../include/QtCore/../../src/corelib/tools/qhash.h:665
#19 0xb7ee946d in QSignalMapper (this=0xb7fc2ff4, parent=0x8e1ee18, name=0x8ffb020 "�\030�� ;�\b") at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120
#20 0xb7ee965e in ?? () from /usr/lib/libQtCore.so.4
#21 0xb7ee9f2b in QHash<QObject*, int>::findNode (this=0x8ffb020, akey=@0x0, ahp=0x8) at ../../include/QtCore/../../src/corelib/tools/qhash.h:863
#22 0xb7ee5ca8 in QMetaObject::activate (sender=0x8e1ee18, from_signal_index=29, to_signal_index=30, argv=0xbf80b2bc) at kernel/qobject.cpp:194
#23 0xb7ee60e0 in ~QObject (this=0x8e1ee18) at kernel/qobject.cpp:750
#24 0xb70162b1 in ~QComboBoxListView (this=0xb71fd1e4) at .moc/release-shared/../../widgets/qcombobox_p.h:82
#25 0xb71fd1e4 in typeinfo for QButtonGroup () from /usr/lib/libQtGui.so.4
#26 0x00000002 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

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

Reported using DrKonqi
Comment 1 John Tapsell 2009-07-05 18:05:50 UTC

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