You are not logged in.
Hi everybody!
Since the last update of the KDE to version 3.5.4 and updating kernel26beyond to its latest version I KDE doesn't start any longer. After KDM is started and I logged in my computer loads for 2 seconds an suddenly stops loading anything. Switching to a console works, but whatever I want to do there also hangs. I can't even restart the system after trying to start KDE. Since there was a similar problem last time having startup times around 3 minutes or so I thought I'll give it some time to load. But nothing happened for around 15 minutes. So I had to push the reset button. I installed XFCE to check if it's a general problem, but starting XFCE worked. So does anyone know what the problem might be and how to fix it? Thanks!
BYE
Christian
Offline
Anything of note in your ~/.xsession-errors file?
/path/to/Truth
Offline
Did you find out anything? I have a similar problem ..
Linux user #403491
"Men have called me mad; but the question is not yet settled, whether madness is or is not the loftiest intelligence– whether much that is glorious– whether all that is profound– does not spring from disease of thought– from moods of mind exalted at the expense of the general intellect." - E. A. Poe from Eleonora
Offline
Maybe i've had the same problem...
After i updated kde and kernel26beyond kde crash just everytime i try to do anything (start apps ecc ecc..). I have an ati videocard and i was using the fglrx accel drivers and this was the problem for me. Everything works again if i use vesa or ati (not fglrx) drivers.
Offline
If it's any help, I found that KDE refused to start if /etc/rc.d/network wasn't started. Don't know if it's related, but thought it was worth mentioning.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
If it's any help, I found that KDE refused to start if /etc/rc.d/network wasn't started. Don't know if it's related, but thought it was worth mentioning.
Perhaps KDE uses the loopback device (fake internet device that sends packages back to the computer instead of sending to an internet device), that is also started by the network daemon.
That's happening in gnome too iirc...
Offline
dcop requires lo to be setup, else it won't work. also if you set hostnames that do not match a reachable address or cannot be resolved, x startup may slow down.
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
dcop requires lo to be setup, else it won't work.
Ah, that explains it. Cheers for clearing that up for me
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline