After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343539 - Three users switching leads to blank tty9
Three users switching leads to blank tty9
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.14.x
Other Linux
: Normal minor
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-31 21:10 UTC by Sebastien Bacher
Modified: 2010-07-02 03:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-05-31 21:10:13 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gdm/+bug/40011

"Using dapper's gdm and the "switch user" funcionality available in the "log out" dialog, do:

1. Login as user "A".
2. From A's desktop, switch user and login as "B".
3. From B's desktop, switch user and login as "C".
4. From C's desktop switch back to B (resume session).
5. As B, log out (this returns you to "A").
6. From A's desktop switch user to C (resume session).
7. As C, log out.

After step 7, you find yourself at a blank tty9 with a blinking cursor.

Explanation: users A, B and C are on tty7, tty9 and tty10 by default. When "B" logs out, tty9 becomes blank. When "C" logs out later from tty10, the screen is retuned to tty9. The logic in gdm needs to be changed. When "C" logs out, the user should be returned to tty7 in this situation (or to a new gdm screen).

Please note, this is a bug in the logic of gdm, not a display/video driver issue. It is 100% reproducible on my machine at least."
Comment 1 Brian Cameron 2006-05-31 23:16:59 UTC
I would accept a patch to fix the GDM logic.  Virtual termainals do not work on Solaris, so it is hard for me to work with this feature.
Comment 2 William Jon McCann 2006-11-03 20:04:30 UTC
The way I've been thinking about this lately is that on systems that support VT switching a GDM greeter should run on the first available VT as it is now.  However, when a user authenticates and a session does not yet exist for this user then we can start the session on a new VT.  If the user is already has a session open on an attached display then we should switch to that VT.

Then when any session exits we should switch back to the VT with the greeter running.

Systems/seats that don't support VT switching or when using XDMCP we would just do as we do now.

What do you think?
Comment 3 Brian Cameron 2006-11-06 22:52:09 UTC
This sounds reasonable to me.  I'd accept a patch to make GDM work this way.
Comment 4 Erik Meitner 2010-05-26 02:20:48 UTC
This bug was opened on gdm 2.14.x, yet the exact same symptoms exist in 2.30.2(2.30.2-0ubuntu1). Did the gdm rewrite in 2.21.x not address this issue as is claimed here: http://live.gnome.org/GDM/NewDesign ? 

If this bug was addressed by the 2.21.x rewrite then this bug should be closed and I will open another one. Feedback would be appreciated.
Comment 5 Ray Strode [halfline] 2010-05-26 18:31:17 UTC
we don't do comment 2 yet, but the original bug should be fixed.  If it's not, repurposing this bug it is probably okay.
Comment 6 William Jon McCann 2010-06-04 20:01:39 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 7 Erik Meitner 2010-07-02 03:46:21 UTC
William, do you think that it is possible for this fix to be applied to 2.30.2? If so, could you please reference the commit(s) that fixed this?