systemsettings crashed with SIGSEGV in vfprintf()

[Graham Stark]

Binary package hint: kdebase-workspace

One of a series of problems with audio I've had since the last update. This one happens when I try to select the'multimedia' option in system settings. I tjhink it's related to problems I've had with the xine audio backend, which crashes all the time.

The last thing I did before this latest crash was to install gstreamer0.10-pulseaudio in the hope that I could use this to bypass xine's audio backend. (Can I?)

Hope this helps,

This is KDE Version 4.3.2 on the latest KUbuntu.

Graham

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 21 07:57:53 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/systemsettings
Package: systemsettings 4:4.3.2-0ubuntu7.1
ProcCmdline: /usr/bin/systemsettings -caption System\ Settings -icon preferences-system
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SegvAnalysis:
 Segfault happened at: 0x7f2d0eaaae34 <vfprintf+148>: callq 0x7f2d0eaeaf10 <strchrnul>
 PC (0x7f2d0eaaae34) ok
 source "0x7f2d0eaeaf10" (0x7f2d0eaeaf10) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 vfprintf () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 vfprintf () from /lib/libc.so.6
 __fprintf_chk () from /lib/libc.so.6
 qt_message_output () from /usr/lib/libQtCore.so.4
Title: systemsettings crashed with SIGSEGV in vfprintf()
Uname: Linux 2.6.31-20-generic x86_64
UserGroups: admin audio cdrom dialout floppy lpadmin plugdev sambashare scanner ve video www-data
XsessionErrors:
 (firefox:3845): GLib-WARNING **: g_set_prgname() called multiple times
 (polkit-gnome-authentication-agent-1:4046): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:_IO_vfprintf_internal (s=0x7fff83df02d0,

[Harald Sitter (apachelogger)]

Should be fixed since forever. If not it is definitely fixed for KDE 4.8 in the KCM.