Mir

[regression] u8 desktop session fails to start

Bug #1526505 reported by Kevin DuBois
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Mir development team
0.18
Fix Released
Critical
Mir development team
Mir 0.18.0
mir (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

u8 desktop session fails to start, due to confusion surrounding platform selection (between mesa and kms).
The root cause seems to be that the nested server (as non-root) cannot become drm-master.

This is somewhat related to lp: #1526209 in that this bug has to do with mesa platform selection, which changed in rev3089.
lp: #1526209 was about the client crashing though, and this bug is about the nested server not being able to start, so they seem to be a bit different.

Tags: regression

Related branches

lp:~mir-team/mir/revert-3098
PS Jenkins bot (community): Approve (continuous-integration)
Daniel van Vugt: Approve
Cemil Azizoglu (community): Needs Information
Diff: 126 lines (+11/-29)
5 files modified
src/platforms/mesa/server/kms/platform_symbols.cpp (+3/-21)
src/platforms/mesa/server/x11/graphics/graphics.cpp (+1/-1)
tests/unit-tests/graphics/mesa/kms/test_platform.cpp (+2/-2)
tests/unit-tests/graphics/mesa/x11/test_platform.cpp (+2/-2)
tests/unit-tests/graphics/test_platform_prober.cpp (+3/-3)
Revision history for this message
Kevin DuBois (kdub) wrote :

Confirmed, as seen by both me and Andreas.

tags: added: regression
Revision history for this message
Cemil Azizoglu (cemil-azizoglu) wrote :

Need to make sure '--vt' option is passed to unity8 for the probing logic to select the correct platform driver for nested.

Daniel van Vugt (vanvugt)
Changed in mir:
milestone: 0.18.0 → 0.19.0
assignee: nobody → Mir development team (mir-team)
status: Confirmed → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix committed to lp:mir/0.18 at revision 3182, scheduled for release in Mir 0.18.0

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Invalid in the "Ubuntu" project as the bug never reached distro.

Changed in mir (Ubuntu):
status: New → Invalid
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision 3198, scheduled for release in mir, milestone 0.19.0

Changed in mir:
status: In Progress → Fix Committed
Kevin DuBois (kdub)
Changed in mir:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt)
Changed in mir:
status: Fix Released → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix Released in Mir 0.18.0. Although it's good to mention this bug got different fixes between the 0.18 and 0.19 branches, it's probably still best to only mention it in the changelog for one of them.

Changed in mir:
milestone: 0.19.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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