Bug 1023260 - Fast user switching fails to show target user list
Summary: Fast user switching fails to show target user list
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-25 03:30 UTC by Mark Tinberg
Modified: 2015-06-29 12:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:43:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fast user switching no list of target users (319.71 KB, image/png)
2013-10-25 03:30 UTC, Mark Tinberg
no flags Details

Description Mark Tinberg 2013-10-25 03:30:18 UTC
Created attachment 815992 [details]
fast user switching no list of target users

Description of problem:

testing fast user switching, I created a new user and switched to it on vt7, after a few iterations of switching using gnome and also using Ctrl-Alt-F1/F7 the new test user shows gdm screen with no target user list in the middle.  I can continue to switch using the keyboard but the test user session is unusable

Further investigation shows that there is a GDM screen on vt4 waiting for password input, putting in the password brought me to the test users desktop on vt4, there is still a blank GDM screen on vt7

Attempts from either of the logged in accounts to switch users redirects to vt7, which is blank

[liveuser@localhost ~]$ loginctl
   SESSION        UID USER             SEAT            
         2          0 root             seat0           
         5       1000 liveuser         seat0           
        c1         42 gdm              seat0           
         9       1002 foo              seat0           
        c2         42 gdm              seat0           


I took a screen shot, it lives in /var/lib/gdm

Version-Release number of selected component (if applicable):

GNOME 3.10.1
Radeon HD 7870 GHz Edition

http://fedoraproject.org/wiki/QA:Testcase_radeon_fastuserswitch
Fedora 20 beta livecd

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora End Of Life 2015-05-29 09:38:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 12:43:24 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.