Hello, this is a problem where I don’t know where to look. I’ll describe what I can: Ok, this is the start situation: KDE just got updated to 4.4.x (0 or 1, doesn't matter). The whole system in clean everything (even did a emerge -e world). Now I created a brand new user. With nothing in his home directory. (Especially no .kde* or anything at all really!) Then I do this: Reproducible: Always Steps to Reproduce: 1. Be sure kde 4.4.1 or kde 4.4.0 is installed. 2. Log in to it (kde 4.4). [Yes, this works with any user here.] But to have a clean test case, preferably use a new user with nothing in its home directory. Actual Results: It hangs at the fourth icon (whatever that is, looks like a desktop) of the startup splash screen, and in .xsession-errors, there is the message: plasma-desktop(6253): Communication problem with "plasma-desktop" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " Expected Results: It should start up and log in normally, and present me with the normal desktop. Unfortunately that’s about all I can find. Is there really no place where plasma logs why it failed? Because I somehow expect it to tell me this under Linux. :) So all I can do, is attach “.xsession-errors” and “emerge --info”, as usual. Also as usual, ask me if you need a specific information etc.
Created attachment 222945 [details] .xsession-errors for the new user’s first time.
Created attachment 222947 [details] emerge --info
You probably checked this, but is dbus running? ps ax|grep dbus
Sorry for the long delay. I thought I had answered this already. Yes, dbus, hald, and consolekit all run. It was the first thing I checked. :)
Aditional info: I just tested it again, in a different X session, with a brand new user (as usual), and it still fails. The current output of “ps ax | grep dbus”, after killing (term) all processes of that user, is: $ ps ax|grep dbus 5338 ? Ss 5:08 /usr/bin/dbus-daemon --system 5941 ? S 0:00 dbus-launch --autolaunch 9e7e2292d26e1002516b5e6b48415436 --binary-syntax --close-stderr 5942 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 6077 ? S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session 6078 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 9381 pts/0 S+ 0:00 grep --colour=auto dbus
(In reply to comment #4) > Sorry for the long delay. I thought I had answered this already. > > Yes, dbus, hald, and consolekit all run. It was the first thing I checked. :) > OK, next question: what is your soprano version? Could you please check if your problem is related to bug 304315?
(In reply to comment #6) > OK, next question: what is your soprano version? It’s 2.4.1. > Could you please check if your problem is related to bug 304315? Unless someone added the bug again that was fixed in 2.4.0.1, likely not. :)
Hey, the problem resolved itself. I could install a new ati driver (fglrx) which now finally supports xorg 1.7. So I updated that too, after syncing emerge. And it turns out that solved it. (Although it still is pretty shaky with the resolutions on my 2-screen system.)
