Multiple crashes on shut down. No biggy, but slightly annoying.

[mintlars]

Hey all

A while ago, I started getting multiple sigsev-crashes on shut down/restart. I think this started after an upgrade, but I'm not sure if it's true or not. If it is, I have no idea of which upgrade it was. My Kubuntu is pretty much straight forward 9.10 with minimal installed software from non-official sources (although I do get unsupported and pre-released updates).

These apps crash whenever I'm shutting down or restarting: knetworkmanager, cups (may be the daemon) and plasma (which is particularly annoying because kde restarts plasma before shutting down, eg. a few extra annoying seconds to shut down). These all sigsevs at the same time. I think yakuake could be added to this list to although this seems irregular and only happens once in a while.

So between 3-4 sigsevs on system shut down, popping up the crash dialog and restarting plasma before shutting down. All in all, not a big deal but adds up to a not-so-good kubuntu experience.

So where should I start looking here? Not sure which log-files are important, so please point me to them if you need them.

Thanks in advance.

[verndog]

Re: Multiple crashes on shut down. No biggy, but slightly annoying.

I have opened a bug on those crashes. Read it and "effects me too", if it applies. Thanks.

[mintlars]

Re: Multiple crashes on shut down. No biggy, but slightly annoying.

Thanks. Will be following that bug.

[Zorael]

Re: Multiple crashes on shut down. No biggy, but slightly annoying.

KDE bug 196207

For all the *buntu users having this bug: Please get the latest libc6 package
from the karmic-backports, it provides the corrected glibc version.
Changing to fixed as it is also solved downstream.
If you are on a different distribution and still have this bug, please ask your
distribution for an updated glibc version.

To my knowledge there is no libc6 update in karmic-backports, though. Perhaps one could pull it from Lucid main.

Try starting knetworkmanager after having exported these environmental variables, and then shut it down and see if it exits cleanly.

$ kquitapp knetworkmanager     # should crash here

$ export QT_NO_GLIB=1
$ export MALLOC_CHECK_=""
$ knetworkmanager &

$ kquitapp knetworkmanager     # should exit cleanly here

Obviously your network connection will die when you stop knetworkmanager.

The same thing happens with Konversation, so I now (until further notice) start it with a script that exports these values before running the Konversation binary.