ksysguard crashed with SIGSEGV in SensorModelEntry::color() changing sensor color

[DS]

Steps to reproduce:
On kubuntu, open ksysguard, go to "System Load", right click on "Network History" graph, select Properties -> Sensors tab, change color for receiving bytes and click on apply. ksysguard crashes.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 23 03:10:55 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.2-0ubuntu7
ProcCmdline: kdeinit4:\ ksysguard\ [kdeinit]
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7fd18bf19d80: mov 0x30(%rsi),%edx
 PC (0x7fd18bf19d80) ok
 source "0x30(%rsi)" (0x00000071) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 ?? () from /usr/lib/libkdeinit4_ksysguard.so
 ?? () from /usr/lib/libkdeinit4_ksysguard.so
 ?? () from /usr/lib/libkdeinit4_ksysguard.so
 QMetaObject::activate(QObject*, int, int, void**) ()
 KDialog::slotButtonClicked(int) ()
Title: kdeinit4 crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:SensorModelEntry::color (this=0x41) at /usr/include/qt4/QtGui/qcolor.h:259
FancyPlotter::applySettings (this=0x1a5f1d0)
FancyPlotter::qt_metacall (this=0x1a5f1d0,
QMetaObject::activate ()
KDialog::slotButtonClicked (this=0x1b726d0,

[Jonathan Thomas (echidnaman)]

Fixed in KDE 4.4.