[arch-general] KDE stoped working
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!!
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
(EE) Failed to load module "i810" (module does not exist, 0) I think is this the cause. Did you removed xf86-video-intel package? Or try to use 'intel' instead of 'i810' in xorg.conf
-- Andrea `BaSh` Scarpino Arch Linux Developer
I knew I forgot some info about my system... ;) I'm using KMS+DRI2, no xorg.conf, and I only have xf86-video-intel installed (2.7.1). Xorg is configuring itself just fine... Here is a snippet of /var/log/Xorg.0.log:
(==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.1, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) *LoadModule: "intel"* (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.6.1, module version = 2.7.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "i810" (WW) Warning, couldn't open module i810 (II) UnloadModule: "i810" (EE) Failed to load module "i810" (module does not exist, 0) (II) LoadModule: "vesa" (II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.2.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "fbdev" (WW) Warning, couldn't open module fbdev (II) UnloadModule: "fbdev" (EE) Failed to load module "fbdev" (module does not exist, 0) (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, Mobile Intel® GM45 Express Chipset, Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41 (II) VESA: driver for VESA chipsets: vesa
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used. 2009/5/27 Andrea Scarpino <andrea@archlinux.org>
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
(EE) Failed to load module "i810" (module does not exist, 0) I think is this the cause. Did you removed xf86-video-intel package? Or try to use 'intel' instead of 'i810' in xorg.conf
-- Andrea `BaSh` Scarpino Arch Linux Developer
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used. Yes, I am stupid -.-' you said KDM works, so X works.
try to move ~/.kde4 dir to somewhere and start kde -- Andrea `BaSh` Scarpino Arch Linux Developer
Did that too, without success... 2009/5/27 Andrea Scarpino <andrea@archlinux.org>
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used. Yes, I am stupid -.-' you said KDM works, so X works.
try to move ~/.kde4 dir to somewhere and start kde
-- Andrea `BaSh` Scarpino Arch Linux Developer
On or about Wednesday 27 May 2009 at approximately 15:08:51 Nicolas Bigaouette composed:
Did that too, without success...
2009/5/27 Andrea Scarpino <andrea@archlinux.org>
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used.
Yes, I am stupid -.-' you said KDM works, so X works.
try to move ~/.kde4 dir to somewhere and start kde
-- Andrea `BaSh` Scarpino Arch Linux Developer
Threads like this do not build my confidence for making the jump from kde3 to kde4. Imagine, one crash or weird boot up and you get 5 hours of dorking with "why won't my kde4 start." Nicolas, I've save a few threads on this from the other list, I'll pick through them and if I get anything other than the normal move .kde4 and force a rebuild of the config, I'll post it here. Good luck, and remember -- File the bug report.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
The problem I had was because of me. The KMS boot option needs 3 modules to be built in the initrd. My fault was creating a copy of /etc/mkinitcpio.conf to /etc/mkinitcpio-kms.conf, which creates /boot/kernel26-kms.img. Since this is useless (one can build the three modules in the stock kernel26.img and choose KMS using i915.modeset=1 or i915.modeset=0) So I changed all my machines to that setup, except my workstation which used the old kernel26-kms.img. So reinstalling the (arch) kernel did not fixed it: I needed to rebuild kernel26-kms.img Probably KDE was crashing because of its desktop effects... I'll see for the bug report. Even with this, KDE is a great desktop IMO. 2009/5/29 David C. Rankin, J.D.,P.E. <drankinatty@suddenlinkmail.com>
On or about Wednesday 27 May 2009 at approximately 15:08:51 Nicolas Bigaouette composed:
Did that too, without success...
2009/5/27 Andrea Scarpino <andrea@archlinux.org>
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used.
Yes, I am stupid -.-' you said KDM works, so X works.
try to move ~/.kde4 dir to somewhere and start kde
-- Andrea `BaSh` Scarpino Arch Linux Developer
Threads like this do not build my confidence for making the jump from kde3 to kde4. Imagine, one crash or weird boot up and you get 5 hours of dorking with "why won't my kde4 start."
Nicolas, I've save a few threads on this from the other list, I'll pick through them and if I get anything other than the normal move .kde4 and force a rebuild of the config, I'll post it here. Good luck, and remember -- File the bug report....
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Even with this, KDE is a great desktop IMO. --> same here On Fri, May 29, 2009 at 9:41 PM, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
The problem I had was because of me.
The KMS boot option needs 3 modules to be built in the initrd. My fault was creating a copy of /etc/mkinitcpio.conf to /etc/mkinitcpio-kms.conf, which creates /boot/kernel26-kms.img. Since this is useless (one can build the three modules in the stock kernel26.img and choose KMS using i915.modeset=1 or i915.modeset=0) So I changed all my machines to that setup, except my workstation which used the old kernel26-kms.img. So reinstalling the (arch) kernel did not fixed it: I needed to rebuild kernel26-kms.img
Probably KDE was crashing because of its desktop effects...
I'll see for the bug report. Even with this, KDE is a great desktop IMO.
2009/5/29 David C. Rankin, J.D.,P.E. <drankinatty@suddenlinkmail.com>
On or about Wednesday 27 May 2009 at approximately 15:08:51 Nicolas Bigaouette composed:
Did that too, without success...
2009/5/27 Andrea Scarpino <andrea@archlinux.org>
On 27/05/2009, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
So the problem is not that it is failing to load i810 or vesa, the server just tries to load them but they are not used.
Yes, I am stupid -.-' you said KDM works, so X works.
try to move ~/.kde4 dir to somewhere and start kde
-- Andrea `BaSh` Scarpino Arch Linux Developer
Threads like this do not build my confidence for making the jump from kde3 to kde4. Imagine, one crash or weird boot up and you get 5 hours of dorking with "why won't my kde4 start."
Nicolas, I've save a few threads on this from the other list, I'll pick through them and if I get anything other than the normal move .kde4 and force a rebuild of the config, I'll post it here. Good luck, and remember -- File the bug report....
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
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)" "
this suggests kded didn't run .. maybe try to start it manually and see where it breaks .. or even better start with xterm only and run each kde component one by one. -- damjan
I tried putting "xterm" only in my .xinitrc. Once xterm is launched (without window management..., but otherwise works fine), if I launch manually /usr/lib/kde4/libexec/klauncher it tells me I should not run that manually, that it is started automatically by kdeinit4. If I then try /usr/bin/kded4, I get the same error as reported earlier:
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)" "
Running "startkde" from the xterm I get:
startkde: Starting up... kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kded(10731): 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.
Why can't kded4 connect to my dbus?? 2009/5/27 Damjan Georgievski <gdamjan@gmail.com>
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)" "
this suggests kded didn't run .. maybe try to start it manually and see where it breaks .. or even better start with xterm only and run each kde component one by one.
-- damjan
I used to have the same problem, what I did is this: 1. reinstall kde: pacman -S kde 2. recreate the kms initcpio in my case (your case could be different): mkinitcpio -p kernel26-kms 3. install xf86-video-intel-newest from aur Im not sure which step was the one that actually fix it, but now Im running kde fine I hope it works for you too Good luck On Thu, May 28, 2009 at 7:35 AM, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
I tried putting "xterm" only in my .xinitrc.
Once xterm is launched (without window management..., but otherwise works fine), if I launch manually /usr/lib/kde4/libexec/klauncher it tells me I should not run that manually, that it is started automatically by kdeinit4.
If I then try /usr/bin/kded4, I get the same error as reported earlier:
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)" "
Running "startkde" from the xterm I get:
startkde: Starting up... kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kded(10731): 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.
Why can't kded4 connect to my dbus??
2009/5/27 Damjan Georgievski <gdamjan@gmail.com>
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)" "
this suggests kded didn't run .. maybe try to start it manually and see where it breaks .. or even better start with xterm only and run each kde component one by one.
-- damjan
Thanx for the suggestion. That did fixed it. The problem was with the initrd, which needed to be rebuilt! Thanx a lot ;) 2009/5/28 Juan Diego <juantascon@gmail.com>
I used to have the same problem, what I did is this:
1. reinstall kde:
pacman -S kde
2. recreate the kms initcpio in my case (your case could be different):
mkinitcpio -p kernel26-kms
3. install xf86-video-intel-newest from aur
Im not sure which step was the one that actually fix it, but now Im running kde fine
I hope it works for you too
Good luck
On Thu, May 28, 2009 at 7:35 AM, Nicolas Bigaouette <nbigaouette@gmail.com> wrote:
I tried putting "xterm" only in my .xinitrc.
Once xterm is launched (without window management..., but otherwise works fine), if I launch manually /usr/lib/kde4/libexec/klauncher it tells me I should not run that manually, that it is started automatically by kdeinit4.
If I then try /usr/bin/kded4, I get the same error as reported earlier:
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)" "
Running "startkde" from the xterm I get:
startkde: Starting up... kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kded(10731): 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.
Why can't kded4 connect to my dbus??
2009/5/27 Damjan Georgievski <gdamjan@gmail.com>
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)" "
this suggests kded didn't run .. maybe try to start it manually and see where it breaks .. or even better start with xterm only and run each kde component one by one.
-- damjan
participants (5)
-
Andrea Scarpino
-
Damjan Georgievski
-
David C. Rankin, J.D.,P.E.
-
Juan Diego
-
Nicolas Bigaouette