dx-packages team mailing list archive

[Launchpad Bug Tracker <1316978@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package dbus - 1.6.18-0ubuntu11

---------------
dbus (1.6.18-0ubuntu11) 14.09; urgency=medium

  * write to $XDG_RUNTIME_DIR instead of the users home when creating the
    dbus-session file, so we can start our session even with 100% filled or
    readonly home dir (LP: #1316978)
 -- Oliver Grawert <ogra@xxxxxxxxxx>   Fri, 26 Sep 2014 14:18:38 +0200

** Changed in: dbus (Ubuntu RTM)
       Status: Confirmed => Fix Released

** Changed in: ubuntu-touch-session (Ubuntu RTM)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1316978

Title:
  ubuntu-touch-session needs to be able to start even if the homedir is
  filled to 100%

Status in Ubuntu CI Services:
  New
Status in “android” package in Ubuntu:
  Invalid
Status in “dbus” package in Ubuntu:
  Confirmed
Status in “hud” package in Ubuntu:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu:
  Confirmed
Status in “dbus” package in Ubuntu RTM:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu RTM:
  Fix Released

Bug description:
  When the ~/phablet tree has media files added to it by the user, it is
  possible for the storage space to be filled, and consequently for the
  device not to boot.

  From the OEM project bug:

  "After further investigation this problem was caused by the following:

   1) Files were pushed to ~phablet/xxxx
   2) The files filled the home partition completely
   3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted
   4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created
   5) As there is no running dbus session instance unity8 fails to start

  Clearing space on the home partition allows unity8 to start again."

  Posted here, since following discussion in #ubuntu-touch it has the
  same underlying cause as bug #1270248, also reported on this package.

  Raised as a separate bug, because this was caused by user action,
  rather than simply the system failing to do log housekeeping.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+subscriptions