KDE completely broken

I am having troubles with all KDE apps since a recent upgrade to 3.5.7 from 3.5.5. At first I thought it was related to all the upgrade troubles with expat (which was upgraded to version 2 at the same time) however I am not so sure anymore.

'emerge -puD' reports nothing to update, and 'revdep-rebuild' says everything is kosher. Everything seems to work fine on this box now except for kde apps, and I have not found a single kde app that does work.

I typically use kde as my default WM/Desktop. After the upgrade, when I 'startx' I get nothing but a black screen, except for the mouse cursor, which tracks across the desktop normally. Nothing else has an effect.

So I changed to Fluxbox, and the desktop starts fine. When I attempt to start kde apps from an eterm I get (as example):

Depending on the app, the output is similar, but not always identical. When I use strace when starting I can see that all the apps are segfaulting. I would post output here but the segfaults happen in different places depending on the app. Sometimes it is triggered by a read/write call, sometimes by a mprotect call and so on...

Does anyone have an idea what might be wrong here? I realize I have not posted much useful information to diagnose this, but I am unsure how to troubleshoot further. I will certainly post output of any commands that may help...

System is a Powermac G5, Kernel 2.6.20-gentoo-r5, 64 bit userland.

Thanks for consideration, -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org"...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 -- gentoo-ppc-user [at] gentoo mailing list

darren kirby wrote: > Hello all, > > I am having troubles with all KDE apps since a recent upgrade to 3.5.7 from > 3.5.5. At first I thought it was related to all the upgrade troubles with > expat (which was upgraded to version 2 at the same time) however I am not so > sure anymore. > > 'emerge -puD' reports nothing to update, and 'revdep-rebuild' says everything > is kosher. Everything seems to work fine on this box now except for kde apps, > and I have not found a single kde app that does work. > > I typically use kde as my default WM/Desktop. After the upgrade, when > I 'startx' I get nothing but a black screen, except for the mouse cursor, > which tracks across the desktop normally. Nothing else has an effect. > > So I changed to Fluxbox, and the desktop starts fine. When I attempt to start > kde apps from an eterm I get (as example): > > $ konsole > kbuildsycoca running... > DCOP Cleaning up dead connections. > Kcrash: Application 'konsole' crashing... > $ > > Depending on the app, the output is similar, but not always identical. When I > use strace when starting I can see that all the apps are segfaulting. I would > post output here but the segfaults happen in different places depending on > the app. Sometimes it is triggered by a read/write call, sometimes by a > mprotect call and so on... > > Does anyone have an idea what might be wrong here? I realize I have not posted > much useful information to diagnose this, but I am unsure how to troubleshoot > further. I will certainly post output of any commands that may help... > > System is a Powermac G5, Kernel 2.6.20-gentoo-r5, 64 bit userland. > > Thanks for consideration, > -d

Well, that doesn't sound good. :) Can you try using gdb to get a backtrace? Maybe they're all segfaulting when using the same library/function call. A backtrace from gdb would help us see that.

quoth the Joseph Jezak: > > Well, that doesn't sound good. :) Can you try using gdb to get a > backtrace? Maybe they're all segfaulting when using the same > library/function call. A backtrace from gdb would help us see that. > > -Joe

Thanks for the reply Joe.

Here are a few lines of context around the segfault running konsole and konqueror from strace, as well as links to the full output:

On Wed, Aug 29, 2007 at 09:12:43PM -0600, darren kirby wrote: > It certainly doesn't like the fact my binaries are stripped. Here's > what I could come up with:

You need to recompile it with FEATURES="nostrip" and possibly USE="debug". Don't forget to remove -fomit-frame-pointer from C{,XX}FLAGS, in case you have it. Depending on where the crash happens, you may have to recompile not only KDE, but also other packages from KDE's dependencies.

quoth the Michael Hanselmann: > Hi > > On Wed, Aug 29, 2007 at 09:12:43PM -0600, darren kirby wrote: > > It certainly doesn't like the fact my binaries are stripped. Here's > > what I could come up with: > > You need to recompile it with FEATURES="nostrip" and possibly > USE="debug". Don't forget to remove -fomit-frame-pointer from > C{,XX}FLAGS, in case you have it. Depending on where the crash happens, > you may have to recompile not only KDE, but also other packages from > KDE's dependencies.

Yes, I was afraid of that. I will rebuild kdelibs and kdebase to start, and see where that leads me.

> > You need to recompile it with FEATURES="nostrip" and possibly > > USE="debug". Don't forget to remove -fomit-frame-pointer from > > C{,XX}FLAGS, in case you have it. Depending on where the crash happens, > > you may have to recompile not only KDE, but also other packages from > > KDE's dependencies. > > Yes, I was afraid of that. I will rebuild kdelibs and kdebase to start, and > see where that leads me.

Well, after finding some time to look into this, the problem seems to have solved itself. I rebuilt kdelibs and kdebase as Michael suggested, with FEATURES="nostrip" and now everything seems to work again.

So? Overaggressive optimization from gcc? Overaggressive strip? Who knows. Just thought I would send this in to give the thread some closure.

Thanks everyone, -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org"...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 -- gentoo-ppc-user [at] gentoo mailing list