On Thu, 2016-07-07 at 17:55 +0100, Simon McVittie wrote: > So if you use "xprop -id 4194305" (in this case) to inspect that window, > you should hopefully find a consistent address and pid attached to it.
From .xsession-errors: + eval DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-sLuSaFQHrp,guid=c6cde1c4915175cc58e3b4a7577ea966'; export DBUS_SESSION_BUS_ADDRESS; DBUS_SESSION_BUS_PID=19844; DBUS_SESSION_BUS_WINDOWID=4194305; xprop -id 4194305 _DBUS_SESSION_BUS_PID(CARDINAL) = 19844 _DBUS_SESSION_BUS_ADDRESS(STRING) = "unix:abstract=/tmp/dbus- sLuSaFQHrp,guid=c6cde1c4915175cc58e3b4a7577ea966" So the pid is consistent, but the process doesn't exist either. > > > 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. > > This might help: > > cat > /etc/dbus-1/session-local.conf < > > > > EOF > > (Actually, I'm quite tempted to enable that for all Debian users via > a drop-in in /etc/dbus-1/session.d - dbus-user-session already logs to > syslog, via the systemd Journal, so it would be consistent.) I didn't spot anything obvious in /var/log/syslog (but does that make sense for the session bus?) > > Or you could try running dbus-launch with DBUS_DEBUG_OUTPUT=1 in the > environment, which makes it not close its dbus-daemon's stderr. I get this: Misc error when trying to watch fd 4: Invalid argument Unable to add reload watch to main loopthis watch should have been invalidatedMisc error when trying to watch fd 5: Invalid argument Unable to add reload watch to main loop: (null) -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
