Mir

[regression] Mir gives up too easily - std::exception::what: Failed to find the current VT

Bug #1169020 reported by Daniel van Vugt on 2013-04-15
34
This bug affects 5 people
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/bzr/mir/trunk/src/server/graphics/gbm/linux_virtual_terminal.cpp(70): Throw in function int {anonymous}::find_active_vt_number()
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: Failed to find the current VT

Related branches

Alexandros Frantzis (afrantzis) wrote :

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).

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 :

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 :

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 :

Still happening...

Michał Sawicz (saviq) wrote :

Syncing task from Mir.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers