Public bug reported:

We've been troubleshooting an issue with dbus on:

$ system-image-cli -i
current build number: 115
device name: frieza_arm64
channel: ubuntu-touch/staging/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.d
/75dbus_dbus-launch (pstree):

systemd,1 fixrtc
  `-lightdm,2384
      `-lightdm,2439 --session-child 11 16
          `-dbus-launch,2692 --exit-with-session ubuntu-touch-session
              `-dbus-launch,2747 --exit-with-session ubuntu-touch-session
                  `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 4 
--print-address 6 --session

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://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however, it
won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The
environment is left with the address of the dead session dbus and so
we're left with a bogus environment variable...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-touch-session 0.108+16.04.20161206-0ubuntu1
Uname: Linux 3.10.93+ aarch64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: arm64
Date: Thu Jan  5 19:06:28 2017
PackageArchitecture: all
SourcePackage: ubuntu-touch-session
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ubuntu-touch-session.d.android.conf:
 GRID_UNIT_PX=13
 QTWEBKIT_DPR=1.0
 NATIVE_ORIENTATION=landscape
 FORM_FACTOR=tablet
mtime.conffile..etc.ubuntu-touch-session.d.android.conf: 2016-10-14T08:44:51
upstart.bluez-mpris-proxy.log:
 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.media.Service at :1.1746 found
upstart.obexd.log:
 Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused
 Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused
upstart.plymouth-log.override: manual
upstart.plymouth-shutdown.override: manual
upstart.plymouth.override: manual

** Affects: ubuntu-touch-session (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug arm64 xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1654365

Title:
  Session dbus lauched by /etc/X11/Xsession.d/75dbus_dbus-launch dies
  immediately

Status in ubuntu-touch-session package in Ubuntu:
  New

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-touch/staging/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.d
  /75dbus_dbus-launch (pstree):

  systemd,1 fixrtc
    `-lightdm,2384
        `-lightdm,2439 --session-child 11 16
            `-dbus-launch,2692 --exit-with-session ubuntu-touch-session
                `-dbus-launch,2747 --exit-with-session ubuntu-touch-session
                    `-dbus-daemon,2748 /usr/bin/dbus-daemon --fork --print-pid 
4 --print-address 6 --session

  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://launchpad.net/ubuntu/+source/dbus/1.10.6-1ubuntu3.2 however,
  it won't launch one if DBUS_SESSION_BUS_ADDRESS is set already. The
  environment is left with the address of the dead session dbus and so
  we're left with a bogus environment variable...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-touch-session 0.108+16.04.20161206-0ubuntu1
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Thu Jan  5 19:06:28 2017
  PackageArchitecture: all
  SourcePackage: ubuntu-touch-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ubuntu-touch-session.d.android.conf:
   GRID_UNIT_PX=13
   QTWEBKIT_DPR=1.0
   NATIVE_ORIENTATION=landscape
   FORM_FACTOR=tablet
  mtime.conffile..etc.ubuntu-touch-session.d.android.conf: 2016-10-14T08:44:51
  upstart.bluez-mpris-proxy.log:
   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.media.Service at :1.1746 found
  upstart.obexd.log:
   Failed to connect to socket /tmp/dbus-lf2wBKftE7: Connection refused
   Failed to connect to socket /tmp/dbus-ej3pH8DVYy: Connection refused
  upstart.plymouth-log.override: manual
  upstart.plymouth-shutdown.override: manual
  upstart.plymouth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1654365/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to