systemsettings crashed with SIGSEGV in QDomNode::save()

[Alan Weeks]

Binary package hint: kdebase-workspace

kubuntu 9.04 upgraded from
previously kubuntu 8.04

lots of problems with the upgrade
swap partit not detected,
nVIDIA card would not load X
download was very very slow...finally aborted itself
source files in Outer Mongolia? (just kidding)

Then used alter CD from Telstra BigPond...much better

systemsettings causes PC to hang...HD keeps running

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/systemsettings
NonfreeKernelModules: nvidia
Package: systemsettings 4:4.2.2-0ubuntu2
ProcCmdline: /usr/bin/systemsettings -caption System\ Settings -icon preferences-system
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 QDomNode::save () from /usr/lib/libQtXml.so.4
Title: systemsettings crashed with SIGSEGV in QDomNode::save()
Uname: Linux 2.6.24-20-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:QDomElementPrivate::save (this=0x82cdf18, s=@0xbff7c730,
QDomNodePrivate::save (this=0x82db420, s=@0xbff7c730,
QDomElementPrivate::save (this=0x82db420, s=@0xbff7c730,
QDomDocumentPrivate::saveDocument (this=0x81d4ec0,
QDomNode::save (this=0xbff7c894, str=@0xbff7c730, indent=1)

[Jonathan Thomas (echidnaman)]

As a workaround you can delete ~/.kde/share/apps/systemsettings/systemsettingsui.rc which seems to get corrupted, causing this crash.

[Harald Sitter (apachelogger)]

Hi Alan!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!