kdeinit4 crashed with SIGSEGV

[Sergiu Bivol]

Binary package hint: kde4libs

After the connection with a 3G modem is lost (but not closed), the KDE workspace crashes if the modem is unplugged while the plasma-applet-network-manager still shows that the is connection still established.

This happens often with my ZTE MF637 modem. It used to happen even more often on Jaunty with KDE 4.2.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Jun 13 17:38:41 2009
Disassembly: 0x7f4592c4a025:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.2.90-0ubuntu1
ProcCmdline: kdeinit4:\ plasma-desktop\ [kdeinit]
ProcEnviron:
 LANGUAGE=ro_RO:ro:en_GB:en
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SegvAnalysis: Failure: list index out of range
Signal: 11
SourcePackage: kde4libs
Stacktrace: #0 0x00007f4592c4a025 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kdeinit4 crashed with SIGSEGV
Uname: Linux 2.6.30-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare vboxusers

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Jonathan Thomas (echidnaman)]

If this crash is reproducible, could you please install kdelibs5-dbg and obtain a backtrace as per: https://wiki.ubuntu.com/Backtrace please? Thanks in advance.

[Sergiu Bivol (sergiu-bivol)]

I have successfully reproduced the crash, however this time the kernel crashed instead (leaving me with CapsLock and ScrollLock blinking).

I managed to attach gdb to plasma-desktop and kdeinit4 before the system crashed, but I'm afraid the logs contain nothing useful since plasma had no time to die :)
Will keep trying to crash the desktop and get something useful.

I've opened a separate bug for the kernel crash:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386764

[Jonathan Thomas (echidnaman)]

I believe this is actually plasma-desktop "disguised" as kdeinit4.