Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies immediately
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
ubuntu-touch-session (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
We've been troubleshooting an issue with dbus on:
$ system-image-cli -i
current build number: 115
device name: frieza_arm64
channel: ubuntu-
last update: 2017-01-05 18:30:16
version version: 115
version ubuntu: 20170105.1
version device: 20161014.0
version custom: 20170105.1
I've come to the conclusion as follows:
The session dbus daemon is launched by lightdm through Xsession.
systemd,1 fixrtc
`-lightdm,2384
`
Due to how the touch session is set up, dbus-launch subsequently kills the daemon because of the --exit-with-session option. Not sure exactly how/why this happens yet.
The dbus-launch PID is replaced with upstart:
phablet 2692 13.6 0.1 45948 3688 ? Ss 19:25 0:21 upstart --user
It was fine so far because the session upstart dbus job launched a session dbus regardless. With the change in https:/
=== Workaround ===
It's possible to disable the Xsessions-dbus script by editing /etc/X11/
use-session-dbus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-
Uname: Linux 3.10.93+ aarch64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: arm64
Date: Thu Jan 5 19:06:28 2017
PackageArchitec
SourcePackage: ubuntu-
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
GRID_UNIT_PX=13
QTWEBKIT_DPR=1.0
NATIVE_
FORM_FACTOR=tablet
mtime.conffile.
upstart.
Can't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busCan't get on session busorg.bluez appeared
Bluetooth Adapter /org/bluez/hci0 found
player core.ubuntu.
upstart.obexd.log:
Failed to connect to socket /tmp/dbus-
Failed to connect to socket /tmp/dbus-
upstart.
upstart.
upstart.
description: | updated |
Changed in lightdm (Ubuntu): | |
assignee: | nobody → Robert Ancell (robert-ancell) |
affects: | lightdm (Ubuntu) → dbus (Ubuntu) |
Changed in dbus (Ubuntu): | |
assignee: | Robert Ancell (robert-ancell) → nobody |
I can't see any reason why LightDM could be affecting this - it only sets up the environment and then runs the session. Is this running under Mir? Because /usr/share/ lightdm/ lightdm. conf.d/ 52-ubuntu- touch.conf has:
[SeatDefaults] ubuntu- touch wrapper= /usr/sbin/ ubuntu- touch-lightdm- session r-command= /usr/share/ ubuntu- touch-session/ usc-wrapper
type=unity
user-session=
session-
unity-composito
[LightDM]
minimum-vt=1
Which makes /usr/sbin/ ubuntu- touch-lightdm- session:
if [ -n "$MIR_SOCKET" ]; then
exec $@
else
exec lightdm-session $@
fi
Which suggests under Mir none of the X session code would be run at all?