Bug 874761 - "Log Out" and "Switch User" unavailable after creating second user account in "User Accounts"
Summary: "Log Out" and "Switch User" unavailable after creating second user account in...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedNTH
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 19:15 UTC by Martin
Modified: 2014-09-15 00:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 12:55:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin 2012-11-08 19:15:18 UTC
Description of problem:
"Log Out" and "Switch User" unavailable after creating second user account in "User Accounts"

Version-Release number of selected component (if applicable):
control-center-3.6.1-1.fc18.x86_64
gnome-shell-3.6.1-1.fc18.x86_64

How reproducible:
always

Steps to Reproduce:
1. Open "User Accounts", "Unlock" it, then add second user using "User Accounts" and set password.
2. Close "User Accounts".
3. Open "User menu".
4. Look for logout.
  
Actual results:
"Log Out" and "Switch User" are missing even second user account exists.

Expected results:
"Log Out" and "Switch User" should be made automagically available when is second user account created.

Additional info:
I've found a workaround.
I reopened "User Accounts" and clicked on "Unlock". This is clearly some gsettings bugs like #871914.
When I tried reproduce this, I saw in step 3 that "Log Out" and "Switch User" disappear from "User menu" in subsecond right after openning it.

Comment 1 Matthias Clasen 2012-11-10 01:18:21 UTC
It does indeed look like the shell looses track of the number of users. I've tried creating and deleting a second user a few times, and invariably, after a while, logout and suspend get 'stuck on'.

Comment 2 Kamil Páral 2012-11-14 18:46:10 UTC
Discussed at 2012-11-14 blocker bug meeting: This doesn't hit any common use cases for live images, has a relatively simple workaround and could be fixed with an update - rejected as NTH for F18 beta.

Comment 3 Fedora End Of Life 2013-12-21 09:19:39 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 4 Fedora End Of Life 2014-02-05 12:55:53 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.