Red Hat Bugzilla – Bug 15699
kdeinit consistently drops core
Last modified: 2008-05-01 11:37:57 EDT
On a machine where "everything" was installed an attempt to start KDE
(on a 'root' account - there is no other account on a test box in this
moment) constitently leaves 2240512 bytes of core and a progress bar
on KDE startup at 33%.
'gdb' provides the following information from 'core':
Core was generated by `kdeinit: konquero'.
Program terminated with signal 11, Segmentation fault.
#0 0x4000bf0b in ?? ()
Attached is all text I managed to grab from a screen. I could not
find anything else in other locations.
The machine is 750 MHz Athlon with 128 MB of memory and Matrox G400
AGP (16 MB of video memory) graphics card configured by Anaconda to
use SVGA server from 3.3.6 version of XFree86.
Created attachment 2235 [details]
messages left on a console screen by KDE
It's actually an autorun problem - rpm -e autorun fixes it.
It's also fixed in the current version.
I am afraid that an experiment contradicts that this is 'autorun' fault.
After 'rpm -e autorun', a check that no 'autorun' process was left around
and removal of an old ~/.kde I have still KDE stuck at the same 33%
progress bar for "Session" as before and a message on a console which looks
the same as before.
The only difference is that now a toolbar showed up at a screen bottom
with an empty main menu, a box in a middle of screen has all buttons
light green, and there is a bunch of icons on a toolbar which only reacts
with alerts that things like "file:/usr/share/applnk//Home.desktop"
(note double slash) does not exist. Indeed, it does not.
That's the other bug that was fixed in rawhide. You can work around that by
opening any KDE app and logging out; the next time you start KDE it will work.