Mir

VTs become blank and unusable after "sudo stop lightdm"

Bug #1224252 reported by Daniel van Vugt
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Incomplete
Medium
Unassigned
Mir
Confirmed
Medium
Unassigned
Unity System Compositor
Confirmed
Medium
Unassigned
mir (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

VTs become blank and unusable after "sudo stop lightdm".

All I want to do is stop unity-system-compositor so I can run and test my own server. So I:
  sudo stop lightdm
This works, but it leaves me with a black screen and no opportunity to switch VTs. The system is essentially unusable till you ssh in and "sudo start lightdm".

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

And now it's not reproducible :/

Changed in lightdm:
status: New → Incomplete
Changed in mir:
status: New → Incomplete
Changed in unity-system-compositor:
status: New → Incomplete
Revision history for this message
Eleni Maria Stea (hikiko) wrote :

I managed to reproduce the bug in Intel.
and it seems to be related to: https://bugs.launchpad.net/mir/+bug/1206633
I'll get a look at it!

Changed in lightdm:
status: Incomplete → Confirmed
Changed in mir:
status: Incomplete → Confirmed
Changed in unity-system-compositor:
status: Incomplete → Confirmed
Changed in mir:
assignee: nobody → Eleni Maria Stea (hikiko)
Daniel van Vugt (vanvugt)
description: updated
Revision history for this message
Robert Ancell (robert-ancell) wrote :

I think it's unlikely that LightDM is causing this, but that u-s-c/mir is not shutting down cleanly when requested.

Changed in mir:
importance: Undecided → High
Changed in unity-system-compositor:
importance: Undecided → High
Changed in lightdm:
status: Confirmed → Incomplete
importance: Undecided → Medium
Revision history for this message
Eleni Maria Stea (hikiko) wrote :

Yes, it seems that it's mir related.
After I upgraded my system, I still get the crash but I can't switch VTs from ssh anymore (with chvt N) which is quite strange.
I was running Mir and X at the same time when I first got the new crash but I don't know if this is related..

Revision history for this message
Eleni Maria Stea (hikiko) wrote :

If I ran a `ps aux` at the time of the crash and grep for X, mir, lightdm only the xorg.failsafe is running. Then if I start lightdm from init,
# /etc/init.d/lightdm start returns the following error:
http://paste.ubuntu.com/6183324/
which is the same when I kill the xorg.failsafe and start lightdm.
I don't know if these messages are relevant to the crash to be honest.
Did anyone get the same issue? Can you switch VTs after the crash?

Eleni Maria Stea (hikiko)
Changed in mir:
assignee: Eleni Maria Stea (hikiko) → nobody
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If the cause of this bug is a crash, it would become a duplicate of bug 1189770 I think.

kevin gunn (kgunn72)
summary: - VTs become blank and unusable after "sudo stop lightdm"
+ [xmir] VTs become blank and unusable after "sudo stop lightdm"
tags: added: xmir
Changed in mir:
importance: High → Medium
Changed in unity-system-compositor:
importance: High → Medium
Daniel van Vugt (vanvugt)
summary: - [xmir] VTs become blank and unusable after "sudo stop lightdm"
+ VTs become blank and unusable after "sudo stop lightdm"
tags: removed: xmir
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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