From kde-devel  Thu Mar 31 22:59:26 2011
From: Michael Jansen <kde () michael-jansen ! biz>
Date: Thu, 31 Mar 2011 22:59:26 +0000
To: kde-devel
Subject: Re: Armedslack getting ready for release and cannot run KDE 4.5.5
Message-Id: <1501721.mCAhioaa24 () gambit ! local ! michael-jansen ! biz>
X-MARC-Message: https://marc.info/?l=kde-devel&m=130161236607367


> --- snip -------
> 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." "

This happens if kuniqueapplications forks and the fork dies. Why the fork dies 
is the question. And we will not know unless we see a backtrace.

> QMetaObject::invokeMethod: No such method
> KUniqueApplication::loadCommandLineOptionsForNewInstance()

This is a normal message after a dfaure special hack iirc. I thought we did 
something against it. David? Or did we just document the hack?

> QDBusObjectPath: invalid path ""

Happens all the time.

> kded(3297)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
> QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought
> it was ':1.5'

I have that a thousand times, just look in your .xsession-error

> Try "qdbus" on a textshell, but a real core dump will be nice as well ;-)

Not nice ... the only way to help.

> 
> Cheers,
> Thomas
> 
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<