Summary: | There's a problem with KDE apps' communication to dbus | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Hasan Ceylan <hceylan> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | kdelibs-bugs, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
xsession-errors
list of rpms |
Description
Hasan Ceylan
2010-01-17 18:17:08 UTC
Created attachment 39984 [details]
xsession-errors
Created attachment 39985 [details]
list of rpms
There are no QtDBus errors in the paste. So I'm removing myself from the list. The following error messages indicate problems in other programs: Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection (Those are ConsoleKit design flaws in its specification) The following error (that appears several times) indicates a bus problem. It's also not a KDE bug. 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." " Thanks for the time, The reason I think this was a KDE problem, after the login process finished, the above mentioned programs start immediately, and successfully communicating with the dbus. How about that? |