[regression] Mir gives up too easily - std::exception::what: Failed to find the current VT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Mir |
Triaged
|
Medium
|
Daniel van Vugt | |
| mir (Ubuntu) |
Medium
|
Unassigned |
Bug Description
I have always run Mir from an ssh login, but also made sure I have a VT1 login on the console too. This has worked well until recently. Now we seem to have introduced a restriction that mir can only be started from the physical console...
$ bin/mir
ERROR: /home/dan/
Dynamic exception type: boost::
std::exception:
Related branches
- Mir development team: Pending requested 2016-08-03
-
Diff: 327 lines (+67/-110)2 files modifiedsrc/platforms/mesa/server/kms/linux_virtual_terminal.cpp (+54/-96)
tests/unit-tests/graphics/mesa/kms/test_linux_virtual_terminal.cpp (+13/-14)
Alexandros Frantzis (afrantzis) wrote : | #1 |
Daniel van Vugt (vanvugt) wrote : Re: [regression] std::exception::what: Failed to find the current VT, when running as non-root on a pseudo terminal | #2 |
Confirmed that root can run mir from ssh. Only non-root can't.
summary: |
- [regression] std::exception::what: Failed to find the current VT + [regression] std::exception::what: Failed to find the current VT, when + running as non-root on a pseudo terminal |
Changed in mir: | |
status: | New → Triaged |
Changed in mir: | |
importance: | Medium → Low |
tags: | added: vt |
tags: |
added: regression removed: regression-update |
Daniel van Vugt (vanvugt) wrote : | #3 |
I've been playing with Mir in a chroot on an armhf chromebook recently and this error is presently a blocking issue. I'm pretty sure my system does not even have VTs, and while it does use the mesa-kms driver, the inability to find or control VTs should not be considered an error.
summary: |
- [regression] std::exception::what: Failed to find the current VT, when - running as non-root on a pseudo terminal + [regression] Mir gives up too easily - std::exception::what: Failed to + find the current VT |
Changed in mir: | |
importance: | Low → Medium |
Changed in mir: | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
Changed in mir: | |
status: | Triaged → In Progress |
milestone: | none → 0.25.0 |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Daniel van Vugt (vanvugt) wrote : | #4 |
No longer a critical priority for the new device bring-up. Might finish it at a later date.
Changed in mir: | |
status: | In Progress → Triaged |
milestone: | 0.25.0 → none |
Daniel van Vugt (vanvugt) wrote : | #5 |
Still happening...
Michał Sawicz (saviq) wrote : | #6 |
Syncing task from Mir.
This should work when running as root. I can add some more logic, so that if the user that is trying to run mir is logged in any VT, then mir will be able to find the current VT, regardless of whether it is the VT the user is logged in. I think this should allow you to work as before (of course, proper VT switching will still not work if your run as a normal user).