Re: Every KDE App Crashes
Hi, I am having also problems with the KDE Crash Handler Dialog, and the whole kde interface. Unfortunaly I am running a system which is not up-to-date. I installed it from Suse distro 9.0. This behaviour exist on my system when I update a shared library. This library is opened by kdeinit. Maybe this could give some info for you. I have to update many systems with a kind of self made distro. I have destilated my update proces, some how that I know which part made the system unstable. The problem:cp /libasound.so.* -> /usr/lib/ after this the whole systems is behaviour is unstable. even after cmd: ldconfig, It does not stabelise. eq. - pressing makes the 'KDE Crash Handler Dialog' apears. - after logging out, the system is busy for a very long time So does anybody know a way to update 'nicely' shared libraries on a running system ?? after while a reboot is no problem. but now I is not possible to reboot at all because of a hang of about minutes. For now, if some body has a hint or tip. Please feel free to send to my private mail. Best Regards, Edwin.. [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Every KDE App Crashes
Hi, I am having also problems with the KDE Crash Handler Dialog, and the whole kde interface. Unfortunaly I am running a system which is not up-to-date. I installed it from Suse distro 9.0. This behaviour exist on my system when I update a shared library. This library is opened by kdeinit. Maybe this could give some info for you. I have to update many systems with a kind of self made distro. I have destilated my update proces, some how that I know which part made the system unstable. The problem:cp /libasound.so.* -> /usr/lib/ after this the whole systems is behaviour is unstable. even after cmd: ldconfig, It does not stabelise. eq. - pressing makes the 'KDE Crash Handler Dialog' apears. - after logging out, the system is busy for a very long time So does anybody know a way to update 'nicely' shared libraries on a running system ?? after while a reboot is no problem. but now I is not possible to reboot at all because of a hang of about minutes. For now, if some body has a hint or tip. Please feel free to send to my private mail. Best Regards, Edwin.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Every KDE App Crashes
I want to thank everyone who gave me advice about this problem... turns out it was not KDE after all. While going through the debian-kde archive I noticed the neat little trick to turn off all those KIconLoader warnings and once I did that I was left with "the App so and so is crashing" and a whole bunch of XLib warnings about GLX not being installed. Well, wouldn't you know it, the GLX module had been commented out of my XF86Config-4 file. Once I uncommented it, everything worked like a charm. So... mystery solved... although I still wonder why KDE would care about the GLX module, and more interestingly, only while exiting. -Sean -- Sean Kellogg 2nd Year - UW Law School c: 206.498.8207e: [EMAIL PROTECTED] w: http://www.livejournal.com/users/economyguy/ <-- lazy mans blog "When the only tool you have is a hammer, you tend to treat everything as if it were a nail." -- Abraham Maslow
Re: Every KDE App Crashes
On Thu, 22 Jul 2004 19:47:31 +0200, Patrick Dreker <[EMAIL PROTECTED]> wrote: > This points the blame towards libGL (OpenGL). Try reinstalling the associated > packages. In SID libGL.so.1 is provided by the packages nvidia-glx (part of > NVidia's proprietary X driver) and xlibmesa-gl (OpenGL software rendering, > part of XFree86). Arrrgh, now that I read this i remember... This was exactly the problem, I don't know how I could have forgotten this. :-/ Actually, I'm running nVidias binary drivers from the related non-free packages. I installed those just before the problem started and forgot to fix /etc/X11/XF86Config-4. The following is related to `Section "Module" ' from X's config. In case you are running nVidia drivers make sure that it does _not_ contain the lines: Load "GLcore"' Load "dri" but only: Load "glx" as described in the README. Bjoern
Re: Every KDE App Crashes
Am Donnerstag, 22. Juli 2004 16:05 schrieb Patrick Dreker:
> Am Donnerstag, 22. Juli 2004 10:52 schrieb Sean Kellogg:
> To really see whether me assumption about the libraries is right, I'd need
> to see at least two backtraces of different apps crashing in the described
> way, to see, if there are similarities. You can send me the backtraces via
> private mail if you'd like, or send them to the list. You can cull all the
> "content-free" lines from the BT ("no debugging symbols found"), so the BTs
> don't get too long. I'll take a look, but no promises
OK, the backtraces (sent by private mail) both show this in common:
---
#3 0x4139b69a in glXChannelRectSyncSGIX () from /usr/lib/libGL.so.1
#4 0x080674e8 in ?? ()
#5 0x413c9fa0 in ?? () from /usr/lib/libGL.so.1
#6 0x080674e8 in ?? ()
#7 0x4139d656 in glXChannelRectSyncSGIX () from /usr/lib/libGL.so.1
This points the blame towards libGL (OpenGL). Try reinstalling the associated
packages. In SID libGL.so.1 is provided by the packages nvidia-glx (part of
NVidia's proprietary X driver) and xlibmesa-gl (OpenGL software rendering,
part of XFree86).
If you are using Nvidia's proprietary drivers try reinstalling the complete
driver package either bei recompiling it from the debian installer packages
(nvidia-kernel-source, nvidia-glx). Perhaps there simply is a mismatch
between the driver itself and the associated nvidia-glx package. If you
installed the driver "manually" (using Nvidia's installer) try completely
removing and reinstalling the package.
Hope this helps.
Patrick
--
Patrick Dreker
GPG KeyID : 0xFCC2F7A7 (Patrick Dreker)
Fingerprint: 7A21 FC7F 707A C498 F370 1008 7044 66DA FCC2 F7A7
Key available from keyservers
pgpGeEmKPWY2F.pgp
Description: signature
Re: Every KDE App Crashes
> Does anyone have any suggestions? > -Sean I had several problems in the past 12 months that were similar. Try the following: - apt-get update, apt-get dist-upgrade - reboot - stop kdm/x11, remove all tmp kde and start kdm/x11 again - take one crashing app, find out its packet and reinstall it (remove it from /var/cache/apt/archives first) - find the packets it depends on, reinstall them (remove them from /var/cache/apt/archives first) - do not prelink (i had a problem with qtlibs just a few weeks ago, crashing all KDE apps) broken packages happened to me twice. after downloading and installing again it was fine. the worst thing is, you have to guess which packet it is. in your case, try the qt and kde packets (please find out the real names yourselv). Tim
Re: Every KDE App Crashes
On Thu, 22 Jul 2004 01:52:37 -0700, Sean Kellogg <[EMAIL PROTECTED]> wrote: > My Debian/Unstable media box running the most current KDE behaves exactly as > expected except when I terminate a KDE application such as KEdit, Konsole, or > KControl. When I terminate it (either alt+F4, quit from the menu, or click > on the little X) the app closes fine, but then a KDE Crash Handler Dialog > comes up. It informs me that there has been a crash of type SIGSEGV for > whatever app I happen to be running. The Backtrace is of little help, but I > could include it if someone knows what to do with it. I can close the dialog > box and there seem to be no ill after-effects, I can restart the app without > a hitch. I recognized the very same behaviour, but can't give a solution, because it works fine for me now. So here's what happened: The problem lasted for about 3 weeks until a few days ago. Restarting KDE didn't work. I finally came to my mind that incompatibilities between the 3.2.3 kdelibs and the 3.2.2 apps could be the cause. That was wrong. I even tried to recompile everything except kdelibs with apt-build which as well didn't solve the issue. Some day I had to reboot the machine and *pooofff* everything worked fine. I don't think that I could help you but wanted to show, that you're not alone. ;-) Bjoern
Re: Every KDE App Crashes
Am Donnerstag, 22. Juli 2004 10:52 schrieb Sean Kellogg:
> My Debian/Unstable media box running the most current KDE behaves exactly
> as expected except when I terminate a KDE application such as KEdit,
> Konsole, or KControl. When I terminate it (either alt+F4, quit from the
> menu, or click on the little X) the app closes fine, but then a KDE Crash
> Handler Dialog comes up. It informs me that there has been a crash of type
> SIGSEGV for whatever app I happen to be running. The Backtrace is of
> little help, but I could include it if someone knows what to do with it. I
> can close the dialog box and there seem to be no ill after-effects, I can
> restart the app without a hitch.
>
> To add some additional mystery... non-KDE apps, like Mozilla or Mplayer,
> have no issues. But, even MORE strange, is that Konqueror doesn't have the
> issue, just the rest of the KDE apps. I assume that it means Konqueror
> never actually terminates. Additionally, when logging in through KDM,
> there are multiple crashes as things like KDM and Ksplash come and go. Oh,
> and it effects all users on the system, so I can't imagine its a setting in
> $HOME/.kde folder.
From experience I'd say that this point towards a damaged or incorrectly
installed library, probably in kdelibs or libqt. This would also explain why
non-KDE apps work fine. Concerning konqueror, you are right, konqueror
normally does not really terminate if you close the window.
To really see whether me assumption about the libraries is right, I'd need to
see at least two backtraces of different apps crashing in the described way,
to see, if there are similarities. You can send me the backtraces via private
mail if you'd like, or send them to the list. You can cull all the
"content-free" lines from the BT ("no debugging symbols found"), so the BTs
don't get too long. I'll take a look, but no promises
> I know its not a package problem, because my laptop and main desktop are
> working fine running the same Unstable KDE packages.
As stated previously I would no exclude a packing problem too easily, but it
would be more like a corrupt file somewhere instead of a general problem with
a package.
Patrick
--
Patrick Dreker
GPG KeyID : 0xFCC2F7A7 (Patrick Dreker)
Fingerprint: 7A21 FC7F 707A C498 F370 1008 7044 66DA FCC2 F7A7
Key available from keyservers
pgp3T9GtCQu33.pgp
Description: signature
Every KDE App Crashes
I've checked back 3 months on the mailing list and there was nothing like this, so please don't shoot me if it has come up before! My Debian/Unstable media box running the most current KDE behaves exactly as expected except when I terminate a KDE application such as KEdit, Konsole, or KControl. When I terminate it (either alt+F4, quit from the menu, or click on the little X) the app closes fine, but then a KDE Crash Handler Dialog comes up. It informs me that there has been a crash of type SIGSEGV for whatever app I happen to be running. The Backtrace is of little help, but I could include it if someone knows what to do with it. I can close the dialog box and there seem to be no ill after-effects, I can restart the app without a hitch. To add some additional mystery... non-KDE apps, like Mozilla or Mplayer, have no issues. But, even MORE strange, is that Konqueror doesn't have the issue, just the rest of the KDE apps. I assume that it means Konqueror never actually terminates. Additionally, when logging in through KDM, there are multiple crashes as things like KDM and Ksplash come and go. Oh, and it effects all users on the system, so I can't imagine its a setting in $HOME/.kde folder. I know its not a package problem, because my laptop and main desktop are working fine running the same Unstable KDE packages. Does anyone have any suggestions? -Sean -- Sean Kellogg 2nd Year - UW Law School c: 206.498.8207e: [EMAIL PROTECTED] w: http://www.livejournal.com/users/economyguy/ <-- lazy mans blog "When the only tool you have is a hammer, you tend to treat everything as if it were a nail." -- Abraham Maslow
