Starting an app in an LXD type container may fail due to not finding the dbus bridge socket

Bug #1654647 reported by Christopher Townsend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
High
Larry Price
Trunk
Fix Released
High
Larry Price
libertine (Ubuntu)
Fix Released
High
Larry Price

Bug Description

I have installed Terminator in my LXD based container, and it fails to start with the following:

(terminator:165): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /run/user/1000/libertine/dbus-s8wkkpog: No such file or directory
Traceback (most recent call last):
  File "/usr/bin/terminator", line 118, in <module>
    TERMINATOR.create_layout(OPTIONS.layout)
  File "/usr/share/terminator/terminatorlib/terminator.py", line 265, in create_layout
    window, terminal = self.new_window()
  File "/usr/share/terminator/terminatorlib/terminator.py", line 192, in new_window
    terminal = maker.make('Terminal')
  File "/usr/share/terminator/terminatorlib/factory.py", line 94, in make
    output = func(**kwargs)
  File "/usr/share/terminator/terminatorlib/factory.py", line 106, in make_terminal
    return(terminal.Terminal())
  File "/usr/share/terminator/terminatorlib/terminal.py", line 178, in __init__
    self.reconfigure()
  File "/usr/share/terminator/terminatorlib/terminal.py", line 782, in reconfigure
    self.titlebar.update()
  File "/usr/share/terminator/terminatorlib/titlebar.py", line 113, in update
    title_font = pango.FontDescription(self.config.get_system_prop_font())
  File "/usr/share/terminator/terminatorlib/config.py", line 371, in get_system_prop_font
    '/desktop/gnome/interface/font_name')
glib.GError: No D-BUS daemon running

Seems the /run/user/1000/libertine bind-mount is not being set up before the application launches.

Tags: lxd

Related branches

tags: added: lxd
Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Larry Price (larryprice) wrote :

Yup, turns out the systemd service I was setting up takes far longer to remount /run/user than I thought. We'll just run the script manually before anything else is allowed to start.

Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 363, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Larry Price (larryprice)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.5.1+17.04.20170118-0ubuntu1

---------------
libertine (1.5.1+17.04.20170118-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * Remove the /tmp/.X11-unix umount during LXC container start for operations
    as it seems it's not needed. (LP: #1654650)
  * Remove extra finish_application() in chroot backend.
  * Set container's locale and language based on the host including installing
    necessary language packs. (LP: #1609982)
  * Bump version to 1.5.1.

  [ Larry Price ]
  * Manually execute lxd bind mount script to fix /run/user and remove
    service. (LP: #1654647)
  * Convert results to dicts on operation/application collision in container
    lifecycle managers.
  * Stop bind-mounting /usr/lib/locale and let environment do all the work.
    (LP: #1654648)
  * Mount lxd home directory in $HOME/.local/libertine-container where it
    belongs.
  * Manually wait for lxd container to stop when specified after calling the
    service. (LP: #1655980)
  * Ask for container user password when creating lxd containers. (LP: #1655977)
  * Bind-mount lxd container applications and icons directories into user's
    home directory.

 -- Christopher Townsend <email address hidden> Wed, 18 Jan 2017 14:50:33 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.