Click to See Complete Forum and Search --> : kde can't find kdeinit


htim63
05-31-2003, 10:12 PM
Hello,
I just did the Redhat upgrade to 9.0 from 8.0 from 7.3. All prior upgrades went well. The installation went well till I tried to start kde.

The splash screen complains; "Could not start kdeinit. Check your installation."

I check my .xsession-errors under my secondary user and find,

startkde: Starting up...
/usr/bin/startkde: line 227: 1354 Segmentation fault ksplash
/usr/bin/startkde: line 231: 1355 Segmentation fault LD_BIND_NOW=true kdeinit +kcminit +knotify
startkde: Could not start kdeinit. Check your installation.
Warning: connect() failed: : No such file or directory
/usr/bin/startkde: line 248: 1357 Segmentation fault kwrapper ksmserver $KDEWM
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.

I haven't done any funky upgrades, this is redhat is "out of the box". I have done some upgrades with RedHat's update. But nothing beyond Redhat packages.

Do I need to reinstall the OS from scratch? I'd hate since it was a pain in the a** to config the video card.

Running a Duron 750 with 256MB of ram. Nvidia MXII

I've attached the startkde script too.

:confused:

GaryJones32
06-01-2003, 11:16 PM
segmentation faults happen when a memory address is accessed that has not been alocated.
this happens all the time when you mis-write a kde type app
but when it happens like this on a tested app
my first thought is physically bad memory
HOWEVER -- since it happened right after your upgrade and
upgrading kde is a tricky thing to say the least
(the configure files are incompatible)
i think i would uninstall kde and qt completely and try again to install it.
if you system runs apt ??
you can
apt-get --purge remove kdelibs4 libarts1
at least that's what you do on debian to get rid of all those pesty
config files that lurk in the kde darkness.

wish i could help more -- that's a tough one
(is everything else working ok??)