You are not logged in.
Pages: 1
Hi guys
I'm not sure if this is KDE or KDEmod but I am no longer able to start KDE. This happens both with startx and logging with KDM.
I did do a 'pacman -Syu' yesterday. I have tried clearing out .kde4 but the same error occurs.
The following error occurs:
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH i686
Current Operating System: Linux lt03869 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 12:47:43 UTC 2009 i686
Build Date: 15 April 2009 11:09:10AMBefore reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 21 10:01:45 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "freetype" (module does not exist, 0)
Link points to "/tmp/kde-skwek"
Link points to "/var/tmp/kdecache-skwek"
Link points to "/tmp/ksocket-skwek"
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: Launched KLauncher, pid = 5274 result = 0
klauncher(5274)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on
"local:/tmp/ksocket-skwek/klauncherMT5274.slave-socket"
kdeinit4: opened connection to :0.0
kdeinit4: preparing to launch /usr/bin/kded4
kdeinit4: Launched KDED, pid = 5275 result = 0
kded(5276)/kdeui (KIconLoader) KPixmapCache::Private::loadIndexHeader: Failed toread index file's header
kded(5275): Communication problem with "kded" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)"
"kdeinit4: PID 5275 terminated.
kdeinit4: preparing to launch /usr/bin/kcminit_startup
kdeinit4: Launched 'kcminit_startup', pid = 5277 result = 0
kcminit(5278)/kdeui (KIconLoader) KPixmapCache::Private::loadIndexHeader: Failedto read index file's header
kdeinit4: PID 5277 terminated.
kdeinit4: Got KWRAPPER 'ksmserver' from socket.
kdeinit4: preparing to launch /usr/bin/ksmserver
<unknown program name>(5273)/ KStartupInfo::createNewStartupId: creating: "lt03869;1242864110;353668;5273_TIME0" :
"unnamed app"
ksmserver(5280)/kdeui (KIconLoader) KPixmapCache::Private::loadIndexHeader: Failed to read index file's header
kdeinit4: PID 5280 terminated.
startkde: Shutting down...
kdeinit4: terminate KDE.
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.waiting for X server to shut down
Offline
I would say to try re-installing KDE, and also you say that you tried cleaning out .kde4 -- did you try just renaming it and letting KDE make a whole new .kde4?
Offline
Hi Ranguvar
Yeah, that's what I meant. I renamed .kde4 and it rebuilt a new one.
I've reinstalled KDEmod but with the same results.
I forgot to mention that KDE does start up. At the splash screen when the picture of the hard disk is about half way faded in is when KDE crashes out.
Thanks
-eskay
Offline
I had the exact same problem as eskay. It began when I was also updating
my laptop... had the same error messages and the same graphical symptoms
(KDE crashes around the HDD icon at the splash-screen).
Also tried as Rangovar suggested, reinstalled KDE to no avail. I even went
further and did "Pacman -Rnc", then did a full reinstall.
Long story short, the cause is that your /var directory is full. So, don't
reinstall or do anything else... just clear up your /var directory and then a
reboot should fix everything.
(1)
Get into a terminal
- reboot into runlevel 3 if KDE has completely and utterly failed. Consult
ArchWiki for the various ways how to.
- or just CTRL+ALT+F2, if your system is still responsive
(2)
Log in as root (or normal user if you really want to... and use sudo or su -).
(3)
Clean up /var by :
- doing "pacman -Sc" is always good
- clearing the old logs (I personally zero-lengthed them... wasn't sure if you
could just delete the files outright)
- deleting the themes in /var/tmp/kdecache-[yourusername]/kpc/
E.g., "rm plasma_theme_Elegance.*" (I deleted all except the default one)
Basically, KDE uses /var/tmp to store lots of stuff related to plasma themes.
So, when it becomes full (e.g., due to your logs or pacman updating its cache
of downloaded packages), KDE cant write to its files... and so, performs the
routine famously known as "epic fail".
Hope this helps out others who encounter the same problem.
Not sure if this can be considered a bug. Should I report it? Or just add
a warning to the KDE page on ArchWiki?
Cheers,
eeg
Last edited by eeg (2009-06-12 19:30:54)
Offline
Pages: 1