[Expired for Mir because there has been no activity for 60 days.]
** Changed in: mir
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648292
Title:
Running
[Expired for mir (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mir (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648292
Incomplete I think is still the correct status here.
Although this bug report has reminded us of some things we don't like
about Mir, it hasn't yet shown that there is an underlying problem in
Mir causing this particular bug.
Unfortunately the log we're seeing from the snap looks kind of
There are two problems being discussed:
/1/ mir doesn't work on the current Ubuntu snappy core kernel for Raspberry pi
2; and,
/2/ Mir does not give good diagnostic information from our attempt at
automaticity deciding on the right graphics stack.
IMO systems that try a series of options (in
Even if we don't have the kernel support in place yet I think Mir could
still do better.
What the user sees is:
Unknown command line options: --vt 1
What that means is:
A non-mesa-kms graphics driver was chosen (or none at all? can't tell). And
that's not even a bug at all if some working
Same problem in mir-kiosk from canonical!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648292
Title:
Running Mir-Server snap, gives error! [Unknown command line options:
--vt 1]
To manage
sorry this happened off my timezone, but I can share with you that the RPi2/3
graphics are not quite ready yet. There is a patch set requiring integration
into the ubuntu kernel that is maintained for RPi. There is work ongoing in the
kernel team now to get these patches integrated, validated
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
So i can't find "mirserver: Selected driver"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648292
Title:
Running Mir-Server snap, gives error! [Unknown command line options:
--vt 1]
To manage
Hi,
As you see, it tries to load it few times.
This is complete syslog for it:
Dec 8 08:11:16 localhost systemd[1]: Started Service for snap application
mir-server.mir-server.
Dec 8 08:11:17 localhost snap[1608]: Mir server snap started
Dec 8 08:11:18 localhost snap[1608]: [2016-12-08
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
Is there another message in the log saying "mirserver: Selected driver:
..."?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648292
Title:
Running Mir-Server snap, gives error! [Unknown command
Thanks for pointing that out. So it's probably not a bug in the snap
itself but a Mir bug.
I have seen this happen before in other bug reports (spurious 'Unknown
command line options: --vt 1' even when the mesa-kms driver is present),
but will need to find those old bug reports...
--
You
** Summary changed:
- Running Mir-Server snap, gives error! (localhost snap[4768]: Unknown command
line options: --vt 1)
+ Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
14 matches
Mail list logo
