On Mon, 2016-07-04 at 17:48 +0100, Simon McVittie wrote:
>
> These indicate that something in your session, whose controlling terminal
> is /dev/pts/0 (?!), used D-Bus and started a dbus-daemon as a side-effect
> ("autolaunching", pid 30347/30348); and in addition, dbus-launch was run
> during your X11 session startup (pid 9702; most likely by
> /etc/X11/Xsession.d/75dbus_dbus-launch). From the fact that pid 9702
> does not have a dbus-daemon child, I think we can infer that it has
> latched onto some other dbus-daemon - hopefully 30348 - advertised in
> a hidden X11 window by some other dbus-launch - hopefully 30347.
Besides reporting upstream, I've tried to investigate a bit here. When running
the first time, I have:
corsac 27662 0.2 0.0 44372 4596 ? Ss 15:45 0:00
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
corsac 27661 0.0 0.0 43696 392 ? S 15:45 0:00
/usr/bin/dbus-launch --exit-with-session --sh-syntax
and with some set -x added to the right places I get some debug from the
session startup in .xsession-errors:
+ . /etc/X11/Xsession.d/75dbus_dbus-launch
+ STARTDBUS=
+ DBUSLAUNCH=/usr/bin/dbus-launch
+ has_option use-session-dbus
+ [ != # $Id: Xsession.options 189 2005-06-11 00:04:27Z branden $
#
# configuration options for /etc/X11/Xsession
# See Xsession.options(5) for an explanation of the available options.
allow-failsafe
allow-user-resources
allow-user-xsession
use-ssh-agent
use-session-dbus ]
+ return 0
+ [ -z ]
+ [ -x /usr/bin/dbus-launch ]
+ STARTDBUS=yes
+ [ -n yes ]
+ /usr/bin/dbus-launch --exit-with-session --sh-syntax
+ eval
DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-6vpeyeGSde,guid=fbf5751317c7c5e0a86c9466577e5ce8';
export DBUS_SESSION_BUS_ADDRESS;
DBUS_SESSION_BUS_PID=27662; DBUS_SESSION_BUS_WINDOWID=12582913;
+
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-6vpeyeGSde,guid=fbf5751317c7c5e0a86c9466577e5ce8
+ export DBUS_SESSION_BUS_ADDRESS
+ DBUS_SESSION_BUS_PID=27662
+ DBUS_SESSION_BUS_WINDOWID=12582913
So DBUS_SESSION_BUS_PID is the pid of dbus-daemon indeed.
When running the second time, I get:
corsac 28763 0.0 0.0 43696 388 ? S 15:52 0:00 /usr/bin/dbus-
launch --exit-with-session --sh-syntax
so no dbus-daemon indeed, and:
+ . /etc/X11/Xsession.d/75dbus_dbus-launch
+ STARTDBUS=
+ DBUSLAUNCH=/usr/bin/dbus-launch
+ has_option use-session-dbus
+ [ != # $Id: Xsession.options 189 2005-06-11 00:04:27Z branden $
#
# configuration options for /etc/X11/Xsession
# See Xsession.options(5) for an explanation of the available options.
allow-failsafe
allow-user-resources
allow-user-xsession
use-ssh-agent
use-session-dbus ]
+ return 0
+ [ -z ]
+ [ -x /usr/bin/dbus-launch ]
+ STARTDBUS=yes
+ [ -n yes ]
+ /usr/bin/dbus-launch --exit-with-session --sh-syntax
+ eval
DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-kkS99bhQSL,guid=74522c6e80d67ea8488e4b35577e5e90';
export DBUS_SESSION_BUS_ADDRESS; DBUS_SESSION_BUS_PID=28764;
DBUS_SESSION_BUS_WINDOWID=4194305;
+
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-kkS99bhQSL,guid=74522c6e80d67ea8488e4b35577e5e90
+ export DBUS_SESSION_BUS_ADDRESS
+ DBUS_SESSION_BUS_PID=28764
+ DBUS_SESSION_BUS_WINDOWID=4194305
so dbus-launch was started correctly and fork()ed dbus-daemon as 28764 but then
something happened:
+ . /etc/X11/Xsession.d/90qt-a11y
+ QT_ACCESSIBILITY=1
+ QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
+ export QT_ACCESSIBILITY QT_LINUX_ACCESSIBILITY_ALWAYS_ON
+ [ -x /usr/bin/dbus-update-activation-environment ]
+ dbus-update-activation-environment --verbose --systemd QT_ACCESSIBILITY
QT_LINUX_ACCESSIBILITY_ALWAYS_ON
dbus-update-activation-environment: error: unable to connect to D-Bus: Failed
to connect to socket /tmp/dbus-kkS99bhQSL: Connection refused
I'll try to investigate why dbus-daemon actually dies the second time (and why
only with lightdm 1.18.2) but any clue welcome.
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
