<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 7, 2014 at 7:43 AM, Kevin Krammer <span dir="ltr"><<a href="mailto:krammer@kde.org" target="_blank">krammer@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On Monday, 2014-01-06, 12:30:43, David L wrote:<br>
> On Mon, Jan 6, 2014 at 2:39 AM, Kevin Krammer wrote:<br>
> > On Sunday, 2014-01-05, 19:39:12, David L wrote:<br>
<br>
</div><div>> > > Perhaps this inconsistency is why I have been having problems.?<br>
> ><br>
> > Yes, that is quite possible.<br>
> > If you look into the session bus file, it also contains a PID. Do you have<br>
> > a<br>
> > process with that PID?<br>
> > If you check the process list, do you have more than one dbus-daemon<br>
> > running?<br>
><br>
> Yes and yes:<br>
> mdm 1580 0.0 0.0 30380 964 ? Ss Jan05 0:00<br>
> //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>
> dgl 1671 0.0 0.0 30380 488 ? Ss Jan05 0:00<br>
> //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>
> dgl 1685 0.0 0.0 31580 1932 ? Ss Jan05 0:00<br>
> //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session<br>
><br>
> 1671 is the pid in the .dbus/session-bus/* file.<br>
<br>
</div>The first one seems to be for a different user, but user dgl is running two<br>
daemons.<br>
<br>
My guess is that the first one, the one which is reachable via the file and<br>
the DISPLAY variable is launched by the X session start as it should.<br>
However, something else seems then to launch another one and that one is then<br>
"seen" by all processes.<br>
<br></blockquote><div>Here is the output from a Linux Mint 15 system after logging in: <br></div><div>102 955 0.0 0.0 24952 2108 ? Ss 08:27 0:00 dbus-daemon --system --fork<br>mdm 1957 0.0 0.0 23856 688 ? Ss 08:27 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>
dgl 2742 0.0 0.0 25032 1776 ? Ss 08:32 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 9 --session<br><br></div><div>Here is the output from a Linux Mint 16 system before logging in:<br>102 678 0.2 0.0 30832 1576 ? Ss 08:41 0:00 dbus-daemon --system --fork<br>
mdm 1426 0.0 0.0 30380 972 ? Ss 08:41 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br><br></div><div>Here is the output from a Linux Mint 16 system after logging in:<br>102 678 0.0 0.0 31432 2240 ? Ss 08:41 0:00 dbus-daemon --system --fork<br>
mdm 1426 0.0 0.0 30380 972 ? Ss 08:41 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>dgl 1820 0.0 0.0 30380 484 ? Ss 08:45 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>
dgl 1836 0.0 0.0 31556 1848 ? Ss 08:45 0:00 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session<br><br></div><div>Using the ajxf flags, it looks like this:<br> 1 678 678 678 ? -1 Ss 102 0:00 dbus-daemon --system --fork<br>
<br> 1 1426 1426 1426 ? -1 Ss 117 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br> 1 1820 1820 1820 ? -1 Ss 1000 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session<br>
1 1836 1836 1836 ? -1 Ss 1000 0:00 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session<br><br></div><div>So indeed Mint 16 has an extra dbus-daemon process owned by me.<br><br>Regards,<br>
<br></div><div> Dave<br><br></div></div></div></div>