touch-packages team mailing list archive

Thread
Date

[Bug 1506707] Re: [regression] Mir server command line options are unpredictable/nondeterministic (--vt is sometimes not recognised)

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>
Date: Mon, 11 Jan 2016 06:50:30 -0000
Reply-to: Bug 1506707 <1506707@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Fix Released in Mir 0.18.0. Although it's good to mention this bug got
different fixes between the 0.18 and 0.19 branches, it's probably still
best to only mention it in the changelog for one of them.

** Changed in: mir
       Status: Fix Committed => Fix Released

** Changed in: mir
    Milestone: 0.19.0 => None

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

Title:
  [regression] Mir server command line options are
  unpredictable/nondeterministic (--vt is sometimes not recognised)

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir server platform command line options are unpredictable/non-
  deterministic.

  I keep thinking I'm imagining things. Sometimes --vt works and
  sometimes it doesn't (from a Gnome Terminal). Well both are true. Now
  I have two separate wily machines with the same packages. One fails
  but the other works:

  FAILING MACHINE:

  $ sudo mir_proving_server --vt 1
  [1444966151.185585] mirplatform: Found graphics driver: mesa-x11
  [1444966151.187021] mirplatform: Found graphics driver: mesa-kms
  Unknown command line options: --vt 1
  $ dpkg -l | grep mir-demos
  ii  mir-demos                                     0.16.0+15.10.20150921.1-0ubuntu1           amd64        Display server for Ubuntu - demonstration programs

  WORKING MACHINE:

  $ sudo mir_proving_server --vt 1
  [1444965570.300933] mirplatform: Found graphics driver: mesa-kms
  [1444965570.302119] mirplatform: Found graphics driver: mesa-x11
  [1444965570.304409] mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
  [1444965570.304465] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.5
  [1444965570.304486] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.5
  [1444965570.305801] mirplatform: Found graphics driver: mesa-kms
  [1444965570.306531] mirplatform: Found graphics driver: mesa-x11
  [1444965570.306617] mirserver: Selected driver: mesa-kms (version 0.16.0)
  ...
  $ dpkg -l | grep mir-demos
  ii  mir-demos                                            0.16.0+15.10.20150921.1-0ubuntu1                      amd64        Display server for Ubuntu - demonstration programs

  It appears the unpredictability might be arising from which driver it
  finds on the filesystem first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1506707/+subscriptions