[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Armedslack getting ready for release and cannot run KDE 4.5.5
From:       Thomas_Lübking <thomas.luebking () gmail ! com>
Date:       2011-03-31 18:46:04
Message-ID: op.vs7022wy9bmiid () localhost ! localdomain
[Download RAW message or body]

Am 31.03.2011, 07:34 Uhr, schrieb John O'Donnell <unixjohn1969@gmail.com>:

> Hi all
>
> getting ready to release Slackware for ARM (armedslack) and we had 4.4.3  
> running
> in armedslack 13.1 quite well.  But lately have been banging our heads  
> against
> the wall with 4.5.5 for quite a while.


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

QMetaObject::invokeMethod: No such method  
KUniqueApplication::loadCommandLineOptionsForNewInstance()
QDBusObjectPath: invalid path ""
kded(3297)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought  
it was ':1.5'

-- /snip ----------

very likely DBus isn't up, connectable (wrong machine, flooded, permission  
problem) or broken.
In consequence "everything" fails :-(

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

Cheers,
Thomas
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]