Please let us know what the "Selected driver" log message was. Or better
yet, attach the full log output.
A similar error was encountered in bug 1355005 and although that bug is
unclear it seems to generally be a case of Mir selecting a driver other
than mesa-kms, and if that happens then such other drivers will reject
the --vt 1 option.
So if you Raspberry Pi is selecting the mesa-kms driver then yes we have
a Mir bug. If it's not and is somehow selecting the Android driver
instead (and if that actually works) only then is it a bug in the snap
(should not be passing --vt 1).
** Changed in: mir
Status: New => Incomplete
** Changed in: mir (Ubuntu)
Status: New => Incomplete
--
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/1648292
Title:
Running Mir-Server snap, gives error! [Unknown command line options:
--vt 1]
Status in Mir:
Incomplete
Status in mir package in Ubuntu:
Incomplete
Bug description:
I don't know, if this is right place!
Trying to run mir-server gives error:
Dec 8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1
Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service:
Main process exited, code=exited, status=1/FAILURE
Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service:
Unit entered failed state.
Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service:
Failed with result 'exit-code'.
Dec 8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service:
Service hold-off time over, scheduling restart.
Running on Raspberry pi 2, Ubuntu snappy core!
runned lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1648292/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
