Re: [gentoo-user] KDE won't start up....

[YoYo Siska <yoyo@gl.ksp.sk>]

On Wed, Jan 04, 2012 at 06:36:59PM +0100, Volker Armin Hemmann wrote:
> Am Donnerstag, 5. Januar 2012, 01:04:53 schrieb Andrew Lowe:
> > Hi all,
> > 	I had a running KDE 4 setup and this afternoon did an:
> > 
> > emerge -NuD world
> > 
> > There were no errors reported, the kernel source had been updated, so I
> > compiled the new kernel, and copied it into place, recompiled my nvidia
> > driver and also evdev drivers and then rebooted the machine. Now, the
> > machine boots up, I get all the usual booting messages, starting ntp,
> > mounting drives, getting IP addresses, exporting nfs and so on, the
> > screen goes black, the hour glass of the KDE log in screen briefly
> > appears then the screen is blanked and I'm back at a text login.
> > 
> > 	I've logged into the machine from the text login and recompiled the
> > kernel, copied it into place, recompiled nvidia and evdev and still the
> > problem persists. I've looked at the xorg & kdm logs and there are  a
> > few errors there that google searches seem to say are OK. The thing that
> > is confusing is that when at the text prompt, I can start up bog
> > standard X via "startx" and the mouse and keyboard work but I can't get
> > KDE to start. Does anyone have any ideas as to what could be causing
> > this problem? Any thoughts on where, besides the two obvious logs, that
> > I can try and track down what's going wrong here, or steps I can take to
> > debug the KDE startup?
> > 
> > 	Any thoughts greatly appreciated,
> > 
> > 		Andrew
> 
> .xsession-errors
> 
> Xorg.0.log
> 
> please. 
> If both are huge, upload them somewhere.
> Also make sure that the permissions of /tmp and /var/tmp are ok. Had it in the 
> past that some update did some very scary things to both places.

Also /var/log/kdm.log would be of use (if you are (well, want to ;)
using KDM as the login manager)... because it seems that the
problem might be with KDM greeter or something similar.

I had it segfaulting once, the symptoms were very similar,  KDM did
bring up X and start kdmgreet which crashed, X went down
immediately, because they had no clients, KDM noticed that X was
running only for a very short time and interpreted  that (correctly) as a
sign that something went wrong and didn't restart the X and insted just
stopped...

that would also explain why running startx works ...

btw, does 
startx /usr/bin/startkde 
start a KDE session?


yoyo