On Monday, 2014-01-06, 12:30:43, David L wrote: > On Mon, Jan 6, 2014 at 2:39 AM, Kevin Krammer wrote: > > On Sunday, 2014-01-05, 19:39:12, David L wrote:
> > > Perhaps this inconsistency is why I have been having problems.? > > > > Yes, that is quite possible. > > If you look into the session bus file, it also contains a PID. Do you have > > a > > process with that PID? > > If you check the process list, do you have more than one dbus-daemon > > running? > > Yes and yes: > mdm 1580 0.0 0.0 30380 964 ? Ss Jan05 0:00 > //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session > dgl 1671 0.0 0.0 30380 488 ? Ss Jan05 0:00 > //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session > dgl 1685 0.0 0.0 31580 1932 ? Ss Jan05 0:00 > //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session > > 1671 is the pid in the .dbus/session-bus/* file. The first one seems to be for a different user, but user dgl is running two daemons. My guess is that the first one, the one which is reachable via the file and the DISPLAY variable is launched by the X session start as it should. However, something else seems then to launch another one and that one is then "seen" by all processes. You could try to find where the second one is coming from, maybe its parent process can be determined in the output of ps axjf or KSysGuard's tree view mode. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
