On Tue, Jan 7, 2014 at 7:43 AM, Kevin Krammer <kram...@kde.org> wrote:
> 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.
>
> Here is the output from a Linux Mint 15 system after logging in:
102 955 0.0 0.0 24952 2108 ? Ss 08:27 0:00
dbus-daemon --system --fork
mdm 1957 0.0 0.0 23856 688 ? Ss 08:27 0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
dgl 2742 0.0 0.0 25032 1776 ? Ss 08:32 0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 9 --session
Here is the output from a Linux Mint 16 system before logging in:
102 678 0.2 0.0 30832 1576 ? Ss 08:41 0:00
dbus-daemon --system --fork
mdm 1426 0.0 0.0 30380 972 ? Ss 08:41 0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
Here is the output from a Linux Mint 16 system after logging in:
102 678 0.0 0.0 31432 2240 ? Ss 08:41 0:00
dbus-daemon --system --fork
mdm 1426 0.0 0.0 30380 972 ? Ss 08:41 0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
dgl 1820 0.0 0.0 30380 484 ? Ss 08:45 0:00
//bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
dgl 1836 0.0 0.0 31556 1848 ? Ss 08:45 0:00
//bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
Using the ajxf flags, it looks like this:
1 678 678 678 ? -1 Ss 102 0:00 dbus-daemon
--system --fork
1 1426 1426 1426 ? -1 Ss 117 0:00 //bin/dbus-daemon
--fork --print-pid 5 --print-address 7 --session
1 1820 1820 1820 ? -1 Ss 1000 0:00 //bin/dbus-daemon
--fork --print-pid 5 --print-address 7 --session
1 1836 1836 1836 ? -1 Ss 1000 0:00 //bin/dbus-daemon
--fork --print-pid 6 --print-address 9 --session
So indeed Mint 16 has an extra dbus-daemon process owned by me.
Regards,
Dave
___________________________________________________
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.
