On 27/05/2009, Nicolas Bigaouette 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

...

On 27/05/2009, Nicolas Bigaouette 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 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.

...

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

...

On 27/05/2009, Nicolas Bigaouette 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

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

...

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

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 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

...

...

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