Is the discussion http://irclogs.ubuntu.com/2014/08/11/%23ubuntu-
mir.html ?
If u-s-c doesn't always accept the --vt option then then it's going to
fail on kernels that have VT support (which from the above log seems to
be this particular case?). If VT support is available then LightDM
assigns VTs to each server / system compositor so they don't conflict.
In the phone case we only have one system compositor but theoretically
you could also start an X server so LightDM has to assign VTs if they
exist.
There seem to options to solve this properly:
1. u-s-c always supports --vt and only applies it for backends that require it.
2. u-s-c backends that use VTs reads the XDG_VTNR environment variable.
I would recommend option 2 since VTs are going to be a legacy feature in
the future anyway and other systems seem to be using XDG_VTNR over
command line options.
** Changed in: lightdm
Importance: Undecided => Medium
** Changed in: lightdm
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355005
Title:
[regression] unity-system-compositor can't start (Unknown command line
options: --vt 1) via lightdm on Android
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1355005/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
