Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT

Bug #1589550 reported by Daniel van Vugt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Incomplete
Undecided
Unassigned
Mir
Expired
Undecided
Unassigned
lightdm (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT.

The result is a black screen, as Unity8 is running but the system defaults to the wrong VT so it's not visible.

Tags: black-screen
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Workaround:

Ctrl+Alt+F8/F9 and I can usually then find Unity8.

tags: added: black-screen
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Is this running with seat type "xlocal" or "unity"?

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Also, please attach a lightdm.log

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Following up on this I've ended up refactoring all this code to fix this bug and others and make it easier to understand.

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

Annoyingly I'm finding Unity8 fails to start on this laptop 50% of the time, for seemingly different reasons each time. Not sure if I can reliably attach logs relevant to this particular bug right now.

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

I think this is causing critical bug 1537389. Although it might be Mir itself failing to VT switch.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Are you affected by bug 1576260? That seems to be making my life difficult in testing this..

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

No I'm not affected by bug 1576260 when I test it but it smells like the same issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Can you try lightdm 1.19.1 / 1.18.2 and see if that solves this?

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

Looking good since around the time bug 1576260 got fixed.

Changed in lightdm:
status: New → Incomplete
Changed in mir:
status: New → Incomplete
Changed in lightdm (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir because there has been no activity for 60 days.]

Changed in mir:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.]

Changed in lightdm (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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