[arch-general] KDE stoped working

[Nicolas Bigaouette]

Hi all,

I'm using KDE 4.2.3 on all my (up-to-date) machines. My workstation crashed
an hour ago so I had to reboot. But then KDE would not launch anymore. I'm
clueless of what could have gone wrong...

I login normaly via KDM, launched as runlevel 5 (inittab). KDM works: I can
enter my login information. Then KDE starts loading. But then, as soon as
the hardrive icon is fuly "unblured", it shutdown and bring me back to KDM.
Same thing if I try via startx (startkde in .xinitrc).

I then get this error in my terminal:

> X.Org X Server 1.6.1
> Release Date: 2009-4-14
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.29-ARCH x86_64
> Current Operating System: Linux soundwave 2.6.29-ARCH #1 SMP PREEMPT Wed
> May 20 06:42:43 UTC 2009 x86_64
> Build Date: 15 April 2009  11:01:49AM
>
>     Before 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: Wed May 27 14:34:14 2009
> (==) Using default built-in configuration (39 lines)
> (EE) Failed to load module "i810" (module does not exist, 0)
> (EE) Failed to load module "fbdev" (module does not exist, 0)
> Setting master
> xset:  bad font path element (#23), possible causes are:
>     Directory does not exist or has wrong permissions
>     Directory missing fonts.dir
>     Incorrect font server address or syntax
> startkde: Starting up...
> kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
> kdeinit4: preparing to launch /usr/bin/kded4
> kded(7702): 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: preparing to launch /usr/bin/kcminit_startup
> kdeinit4: preparing to launch /usr/bin/ksmserver
> startkde: Shutting down...
> klauncher: Exiting on signal 1
> startkde: Running shutdown scripts...
> startkde: Done.
>
> waiting for X server to shut down Dropping master
>

DBus is running:

> > ps aux | grep dbus
> dbus      4157  0.0  0.0   8500   940 ?        Ss   14:50   0:00
> /usr/bin/dbus-daemon --system
> nicolas   6206  0.0  0.0  23864   712 tty2     S    15:03   0:00
> dbus-launch --autolaunch 6f2374eec76b3f19172c118549c7da6d --binary-syntax
> --close-stderr
> nicolas   6207  0.0  0.0   8400   888 ?        Ss   15:03   0:00
> /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
>
and same thing with HAL:
> ps aux | grep hal

> hal       5907  0.0  0.1  28128  4964 ?        Ss   15:02   0:00
> /usr/sbin/hald
> root      5908  0.0  0.0  15680  1188 ?        S    15:02   0:00
> hald-runner
> root      5936  0.0  0.0  17792  1140 ?        S    15:02   0:00
> hald-addon-input: Listening on /dev/input/event4 /dev/input/event2
> /dev/input/event1
> hal       5974  0.0  0.0  15388  1012 ?        S    15:02   0:00
> hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
> root      5976  0.0  0.0  17796  1132 ?        S    15:02   0:00
> hald-addon-storage: polling /dev/sr0 (every 16 sec)
>

I even tried launching "startkde" via strace to see what was happening, but
it seems fine:

> [...]
> stat("/usr/bin/xinit", {st_mode=S_IFREG|0755, st_size=15408, ...}) = 0
> rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
> lseek(255, -217, SEEK_CUR)              = 4276
> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
> child_tidptr=0x7fa98151d7c0) = 7650
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
> rt_sigaction(SIGINT, {0x435840, [], SA_RESTORER, 0x7fa98075f350},
> {0x4467e0, [], SA_RESTORER, 0x7fa98075f350}, 8) = 0
> wait4(-1,
>
> X.Org X Server 1.6.1
> Release Date: 2009-4-14
> X Protocol Version 11, Revision 0
> [...]


Anyone having an idea what could be wrong??

Thanx!!