Ubuntu GNOME: reboot dialog in live image shows 6 versions of the live user logged in on the console

Bug #1347553 reported by Andy Whitcroft on 2014-07-23

This bug report will be marked for expiration in 22 days if no further activity occurs. (find out why)

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Undecided
Unassigned
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

When attempting to shutdown from the power menu on Ubuntu GNOME live session the live session user is shown logged in roughly 6 times on (console). Talking to ~xnox this is likely related to systemd-logind.

Andy Whitcroft (apw) wrote :

Does not appear to occur on the installed system.

It is possible this is related to the emergency holographic shell, but there is only one of those.

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1347553

tags: added: iso-testing
Tim (darkxst) wrote :

I am aware of this issue but it is pretty hard to fix.

Basically what happens is when you goto shutdown gnome-shell, it shows a list of all logged in sessions, this would be completely normal behaviour except, it just so happens that on the live session that all 6 VT's are set to auto-login.

Martin Pitt (pitti) wrote :

As there are actually 6 ttyX logins, this just shows that logind is actually right -- these all need their own logind cgroup/session.

What gnome-shell could potentially do is to only show logins that have a Display; I suspect we don't want to offer graphical fast user switching to text VTs anyway.

Changed in systemd (Ubuntu):
status: New → Invalid
Daniel van Vugt (vanvugt) wrote :

On artful I see a similar issue but only my remote (ssh) logins are listed. Not sure if the original bug still exists.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Daniel van Vugt (vanvugt) wrote :

Also, Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017

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

Other bug subscribers