touch-packages team mailing list archive

[Launchpad Bug Tracker <1371597@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity8 -
8.00+14.10.20140930.2-0ubuntu1

---------------
unity8 (8.00+14.10.20140930.2-0ubuntu1) utopic; urgency=low

  [ Alexandros Frantzis ]
  * Remove stale trusted socket before starting unity8 from upstart (LP:
    #1371597) (LP: #1371597)

  [ CI bot ]
  * Resync trunk

  [ Andrea Cimitan ]
  * Move activity indicator on top of keyboard (LP: #1354519)

  [ Gerry Boland ]
  * Cleanup: Remove unused member and fix small syntax error in
    OrientationLock

  [ josharenson ]
  * Fix lp:1367894 by correcting how the minute value is calculated in
    the panel. (LP: #1367894)

  [ Nick Dedekind ]
  * Fixed DefaultIndicatorPage test. Fixed warnings from test.

  [ Ying-Chun Liu ]
  * Remove maxLineCount in preview. (LP: 1328513) (LP: #1328513)

  [ Michael Terry ]
  * Fix some code that accidentally landed in trunk before it got
    cleaned up. The current code just has some duplication to it that
    should be unified.
  * Implement latest visual designs for passphrase lockscreen.
  * Make it easier to use the Lockscreen component from the welcome
    wizard.
  * Limit how much memory we reserve for the greeter background image,
    allowing giant images to appear correctly.

  [ Daniel d'Andrada ]
  * Add gdbTestComponentName build targets
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Tue, 30 Sep 2014 16:57:28 +0000

** Changed in: unity8 (Ubuntu)
       Status: New => Fix Released

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

Title:
  Stale trusted socket may stop Unity8 from restarting after an abnormal
  exit

Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  In some cases (like bug #1371593) unity8 crashes leaving the
  mir_socket and mir_socket_trusted sockets in the filesystem. When
  unity8 tries to restart it fails with "bind: address already in use"
  because of the left over mir_socket_trusted.

  There are two aspects to this bug:

  1. The unity8 upstart script should clean up the trusted socket before starting, like it does for the normal socket
  2. If Mir is instantiated using the mir::run_mir() helper function, it is able to clean up the sockets even when the server crashes. However unity8 doesn't currently use the helper (also see bug #1371621).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1371597/+subscriptions