Problems with KDE4 under Kubuntu Hardy

[Derek Broughton]

Rosalind Mitchell wrote:

> Hmm...  I can't believe I'm alone with this problem?

Hmm.  I can...  If you weren't the _only_ person having the problem, the
odds would be overwhelming that you'd have already found somebody else
reporting it :-)  (and probably got a solution too)
 
> On Thursday 29 May 2008 16:09:14 Rosalind Mitchell wrote:
>> I've been trying to get KDE4 running on my ADM64 box under Kubuntu Hardy,
>> but it's doing my crust in.  I cannot get it to run beyond the splash
>> screen - it goes through all the motions and then dumps me back in the
>> login screen.

Splash screen, or Login screen?  It sounds to me as if you're getting to the
KDM login screen, entering your username/password, the screen probably
flashes a few times and then puts up the login screen again.

>> I have tried logging into a failsafe session and then running
>>
>> %/usr/lib/kde4/bin/startkde > user.log 2>$1

Probably unnecessary - the same info was probably available in the normal
login from ~/.xsession_errors.  Whenever this happens, it usually shows up
there.

>> which produces this output in user.log:
...
>> kdeinit4: PID 7199 terminated.
>> Hangup
>> GOT SIGHUP
>> Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer:
>> Failed to connect to socket /tmp/dbus-lYPyTxiGsa: Connection refused

I'm not sure how signifant this is - the Dbus error seems to be _after_ kde
has already quit, but I'd want to look at that first, anyway.  It stands to
reason that you'd have trouble if dbus isn't working.  Check the
permissions on that socket first.  Is /usr/bin/dbus-daemon running?  Check
syslog for other dbus errors.

>> No protocol specified
>> xprop:  unable to open display ':0'
>> No protocol specified
>> xprop:  unable to open display ':0'

I haven't a clue why it does this, but they're no really errors - of
_course_ it can't open display :0 when it's already shutting down.
-- 
derek