VOOZH about

URL: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1169020

⇱ Bug #1169020 β€œ[regression] Mir gives up too easily - std::except...” : Bugs : mir package : Ubuntu

πŸ‘ Image

Ubuntu
mir package

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

Bug #1169020 reported by Daniel van Vugt
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Daniel van Vugt
mir (Ubuntu)
Triaged
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

Tags: regression vt

Related branches

lp:~vanvugt/mir/fix-1169020
πŸ‘ Image
On hold for merging into lp:mir
Mir development team: Pending requested
Diff: 327 lines (+67/-110)
2 files modified
src/platforms/mesa/server/kms/linux_virtual_terminal.cpp (+54/-96)
tests/unit-tests/graphics/mesa/kms/test_linux_virtual_terminal.cpp (+13/-14)
api
Revision history for this message πŸ‘ Image
Alexandros Frantzis (afrantzis) wrote : #1

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
Revision history for this message πŸ‘ Image
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
Revision history for this message πŸ‘ Image
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
Revision history for this message πŸ‘ Image
Daniel van Vugt (vanvugt) wrote : #5

Still happening...

Revision history for this message πŸ‘ Image
MichaΕ‚ Sawicz (saviq) wrote : #6

Syncing task from Mir.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

πŸ‘ Launchpad
 β€’  Take the tour  β€’  Read the guide  
Β© 2004 Canonical Ltd.  β€’  Terms of use  β€’  Data privacy  β€’  Contact Launchpad Support  β€’  Blog  β€’  Careers  β€’  System status  β€’  c38ea58 (Get the code!)