KDE crash handler when exiting programs

Klas · 08-22-2004, 03:49 AM

Hi

Once again i have destroyed my mandrake 9.1 system by messing with it to much. This is what i did this time.

I compiled a new kernel (2.6.8), and when i should try it i rebooted. But something was configured wrong and i didnt get a picture on my display. I could hear some activity going on from my disks but after a while i had to reset the box.

I rebooted the box on my usual kernel and i got informed that the system was shut down uncleanly. The box booted up ok though.

The problem appears when i exit KDE programs (like Kmail, konqueror, etc). The KDE crash handler appears telling me that "the program caused the signal 11 SIGSEGV and crashed the program". The output from the crash handler is something like this depending on which program that exits:

Code:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 3880)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x413c6677 in waitpid ()
   from /lib/i686/libpthread.so.0
#0  0x413c6677 in waitpid () from /lib/i686/libpthread.so.0
#1  0x40aecebb in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  0x415323b8 in __libc_sigaction () from /lib/i686/libc.so.6
#3  0x40db480b in qt_cleanup() () from /usr/lib/qt3/lib/libqt-mt.so.3

The error doesnt seem to cause any problems exept the anoying dialog box. Does anybody know how to fix this without reinstaling the whole system?

Klas

Klas · 08-22-2004, 04:37 AM

Hmm i think i solved my problem by reinstalling kdelibs and libqt3. I used Kpackage. Be sure to "replace packages" not just update.

Probably time to update mandrake anyway

Klas

dangerboy · 08-25-2004, 04:59 PM

Reinstalling those libs did not seem to put a dent in it. After the close of *almost* every program, KDE Crash Handler pops up and alerts me of a Signal 11 (SIGSEGV) at the close of the program.

This is especially annoying as I can't start or shutdown my MDK10 box without having to push close at least 20 times. It seems to be doing this only with the KDE based progs like Knotify, Kmix, Konsole, Kdesktop-lock, and even Ksysguard when I press close. Naturally since I am using KDE you can only imagine how frustrating it is to do anything and have to close an extra window after you have successfully worked with a program. The only progs that don't trip the alarm are ones that aren't directly dependent upon KDE like Mozilla, Totem, Audacity, etc.

I just recently installed the newer version of those libs mentioned above and this situation didn't start until I updated my install.

Backtrace does me no good either:

This backtrace appears to be useless.
This is probably because your packages are built in a way which prevents creating of proper backtraces, or the stack frame was seriously corrupted in the crash.

I would imagine it gives me this message as the stack was destroyed when the program closed successfully and it's just an annoying bug. At this point, are there any recommendations? I don't know how to install the previous versions of the libs without completely ruining KDE. Or maybe it's something else? I'm stumped.

Klas · 08-26-2004, 01:25 AM

I bet you are using a Nvidia based graphics card with the latest Nvidia drivers (i do). For some reason i suspect them. This is my best bet right now.

Klas

dangerboy · 08-26-2004, 07:48 AM

You won your bet. I have the latest drivers. I've noticed as well that everyone who has had this problem has also had nVidia drivers as a common element throughout. I think it's too strong to be coinincidence at this point. I wonder if it's possible to install a previous version of the nVidia drivers to see if that changes anything. It's either that or KDE's new release conflicts with the latest nV drivers.

otish1000c · 08-26-2004, 08:02 AM

i haven't run into this problem, per se', but in reference to your nvidia question.........

Quote:

I wonder if it's possible to install a previous version of the nVidia drivers to see if that changes anything.

you can uninstall the drivers by exiting X & then by typing in terminal as root......

Code:

sh NVIDIA-Linux-x86-1.0-XXXX-pkg1.run --uninstall

where XXXX is the version number.

which drivers are you using? the newest .6111? if so, you're one of the lucky few that even got them working. i couldn't get them installed, so i'm still using the 6106 drivers which work fine. there are ways to troubleshoot & get the 6111 drivers going, but i don't have the info here right now & for my purposes it's more trouble than it's worth.

if you uninstall the drivers, make sure you either have different (older) drivers to install to replace them with, or re-edit your XF86Config-4 (or xorg.conf) file for use without the drivers.

otis

Klas · 08-26-2004, 11:37 AM

I ran in to this problem using 6111 anyway.

Klas

dangerboy · 08-26-2004, 04:55 PM

Thank you otis for the howto on the uninstall procedure, but uninstalling NVIDIA 6111 and installing 6106 in its place did nothing. I'm still experiencing the same annoying crashes. I seriously think it's the KDE updates I installed that are causing this. Is there a way to go back a version or 2 without a complete reinstall? If so, how do I install an old rpm over a newer one? Or maybe someone can suggest something less drastic? I appreciate everyone's input, thanx to everyone for the prompt responses. =)

Alex

gaou67 · 08-29-2004, 07:34 AM

Hello yall
I had the same pb since I recently upgrade to kernel 2.6.8 on my mdk, and had to dl the new nvidia kernel mod.
All my kde apps used to crash on shutdown...
I also noticed that glx had been inactivated in the XF86Config-4 script, and, magically, everything went back in order as I add it again :
Load "glx"
in /etc/X11/XF86Config-4

Don't know if it may help... but its worth having a try... ;-)
Good luck !
FX - Strasbourg, FRANCE

dangerboy · 08-29-2004, 11:03 PM

Thanx for the suggestion, but I found a solution through a different method.

After uninstalling and reinstalling every nVidia driver in creation with no change, I begin to notice that no matter what I tried, my XF86Config-4 file always remained the same (ie: the settings listed in it, regardless of what I changed, would return to the OS default). I began to suspect a permissions problem of sorts so I tried setting world permissions to my XF86Config-4 file (using 'chmod 777 XF86Config-4'). Before anyone flames me about this, I know it's not Kosher, but it worked. I unistalled the nVidia drivers after setting world permission and successfully reinstalled 6106 (6111 failed in compilation). I rebooted and noticed an immediate difference. Not only had my XF86Config-4 file changed, but the annoying errors were history. I reset permissions with a rooted instance of Konqueror and I am enjoying the silence of a crash free Distro once again.

Thanx to everyone for your help. I will post the link to this discussion to a few other open threads I've seen.

I love this site.