[regression] unity-system-compositor can't start (Unknown command line options: --vt 1) via lightdm on Android
Bug #1355005 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Light Display Manager |
Incomplete
|
Medium
|
Unassigned | ||
Mir |
Invalid
|
Critical
|
Unassigned | ||
0.6 |
Invalid
|
Critical
|
Unassigned | ||
Unity System Compositor |
Fix Released
|
Critical
|
Alan Griffiths | ||
unity-system-compositor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
From Cemil:
Sync'ed up 0.6 with devel@r1831 since we were in TRAINCON-0. Everything built successfully.
Using image #179 with 0.6, mir itself works (i.e. mir-demos & nested), but USC has the following error :
root@ubuntu-
Unknown command line options: --vt 1
The "vt" option is passed in by the wrapper in lightdm, but not sure why usc is rejecting it. Without 0.6, usc works fine with the same set of args.
It'd be nice if the AUS, or EUR can take a look on Mon. Follow the instructions (updated due to platform versioning) below to install and test :
Changed in mir: | |
milestone: | none → 0.7.0 |
importance: | Undecided → Critical |
summary: |
- [regression] Unknown command line options: --vt 1 + [regression] unity-system-compositor can't start (Unknown command line + options: --vt 1) |
Changed in mir: | |
assignee: | nobody → Mir development team (mir-team) |
status: | New → In Progress |
summary: |
[regression] unity-system-compositor can't start (Unknown command line - options: --vt 1) when run against Mir 0.6/0.7 + options: --vt 1) via lightdm on Android |
Changed in unity-system-compositor: | |
assignee: | nobody → Alan Griffiths (alan-griffiths) |
Changed in unity-system-compositor: | |
status: | Invalid → In Progress |
Changed in mir: | |
assignee: | Mir development team (mir-team) → nobody |
Changed in unity-system-compositor: | |
importance: | Undecided → Critical |
Changed in unity-system-compositor: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Not in progress any more. Blocked by USC bug 1355021.