KDE completely broken

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 
-- 
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-usergentoo.org 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.

-Joe
-- 
gentoo-ppc-usergentoo.org mailing list

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:

konsole:
http://badc
omputer.org/strace_konsole.txt [427K]

 write(3, "221024051H4
2"..., 1044) = 
1044
read(3, "34124051H2f257t205?T".
.., 32) = 32
read(3,
"261A2402724027240n1A
33"..., 32) = 
32
read(3,
"261C2402724027240n1A
2"..., 32) = 32
read(3,
"131u64K`2023)8
20"..., 32) = 
32
readv(3, [{"2>B%m}234M177200]|", 24},
{"", 0}], 2) = 
24
write(3, "e21015", 8)         = 8
read(3,
"161v617377377252620
0"..., 32) = 32
read(3,
""
, 24) = 24
--- SIGSEGV (Segmentation fault)  0 (0) ---

konqueror:
http://ba
dcomputer.org/strace_konqueror.txt [195K]

lstat("/usr", {st_mode=S_IFDIR|0755, st_size=4096,
...}) = 0
lstat("/usr/kde", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
lstat("/usr/kde/3.5", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
lstat("/usr/kde/3.5/share", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
lstat("/usr/kde/3.5/share/apps",
{st_mode=S_IFDIR|0755, st_size=8192, ...}) = 
0
access("/usr/kde/3.5/share/apps", F_OK) = 0
lstat("/usr/kde/3.5/share/apps",
{st_mode=S_IFDIR|0755, st_size=8192, ...}) = 
0
access("/home/bulliver/.kde3.5/share/apps/konqueror/pro
files/webbrowsing", 
R_OK) = 0
stat("/home/bulliver/.kde3.5/share/apps/konqueror/profi
les/webbrowsing", 
{st_mode=S_IFREG|0600, st_size=642, ...}) = 0
--- SIGSEGV (Segmentation fault)  0 (0) ---

kmail dumps this:

kbuildsycoca running...
KCrash: Application 'kmail' crashing...
DCOP aborting (delayed) call from 'anonymous-5590' to
'kmail'
ERROR: Communication problem with kmail, it probably
crashed

My untrained eye cannot see anything wrong with the strace:
http://badcom
puter.org/strace_kmail.txt [58K]
that is, there is no segfault.

I am going to have to read the gdb docs a bit before I can
figure out how to 
use it to get a backtrace. It certainly doesn't like the
fact my binaries are 
stripped. Here's what I could come up with:

  $ gdb konqueror
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as
"powerpc64-unknown-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library
"/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/kde/3.5/bin/konqueror
(no debugging symbols found)
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
(no debugging symbols found)
kbuildsycoca running...
DCOP Cleaning up dead connections.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()

I will have a further play with gdb and post back if I learn
something. I 
guess I will poke around upstream (KDE's) bugzilla and see
if there is 
anything there as well.

Thanks,
-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-usergentoo.org mailing list

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.

Greets,
Michael

-- 
http://hansmi.ch/
-- 
gentoo-ppc-usergentoo.org mailing list

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.

> Greets,
> Michael
>
> --
> http://hansmi.ch/

-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-usergentoo.org mailing list