OK in that case I can't tell what's going wrong. We'll need to look at (or ask the creator of) the snap itself.
The bug can probably stay incomplete because there's not yet sufficient evidence that this is a bug in Mir at all. Perhaps just a bug in the snap definition. -- 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
