Bug 996252

Summary: No possible to login after locking screen
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: admiller, fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:16:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description piio 2013-08-12 18:50:42 UTC
Description of problem:
After update to gnome-shell 3.9.5 I can't login after locking my screen - I see only gray background with bottom panel, but no user accounts.

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

How reproducible:
Always

Steps to Reproduce:
1. Lock screen
2. Try to login

Actual results:
Gray background with bottom panel, but user list not visible

Expected results:
User list

Additional info:
Aug 12 20:20:30 491-0859 gnome-session[3256]: (gnome-shell:3621): Gjs-WARNING **: JS ERROR: Error: second argument to Lang.bind() must be a function, not undefined
Aug 12 20:20:30 491-0859 gnome-session[3256]: bind@/usr/share/gjs-1.0/lang.js:98
Aug 12 20:20:30 491-0859 gnome-session[3256]: SourceActor<._init@/usr/share/gnome-shell/js/ui/messageTray.js:1101
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: _Base._construct@/usr/share/gjs-1.0/lang.js:154
Aug 12 20:20:30 491-0859 gnome-session[3256]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Aug 12 20:20:30 491-0859 gnome-session[3256]: Source<._ensureMainIcon@/usr/share/gnome-shell/js/ui/messageTray.js:1269
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: Source<.getSummaryIcon@/usr/share/gnome-shell/js/ui/messageTray.js:1275
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: SummaryItem<._init@/usr/share/gnome-shell/js/ui/messageTray.js:1394
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: _Base._construct@/usr/share/gjs-1.0/lang.js:154
Aug 12 20:20:30 491-0859 gnome-session[3256]: Class._construct/newClass@/usr/share/gjs-1.0/lang.js:248
Aug 12 20:20:30 491-0859 gnome-session[3256]: MessageTray<._addSource@/usr/share/gnome-shell/js/ui/messageTray.js:1930
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: MessageTray<._onSourceEnableChanged@/usr/share/gnome-shell/js/ui/messageTray.js:2027
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: MessageTray<.add@/usr/share/gnome-shell/js/ui/messageTray.js:1924
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: NotificationDaemon<._getSource@/usr/share/gnome-shell/js/ui/notificationDaemon.js:349
Aug 12 20:20:30 491-0859 gnome-session[3256]: wrapper@/usr/share/gjs-1.0/lang.js:213
Aug 12 20:20:30 491-0859 gnome-session[3256]: NotificationDaemon<.NotifyAsync/<@/usr/share/gnome-shell/js/ui/notificationDaemon.js:451
Aug 12 20:20:30 491-0859 gnome-session[3256]: asyncCallback@/usr/share/gjs-1.0/overrides/Gio.js:91

Comment 1 piio 2013-08-14 08:04:57 UTC
Removing local extension Messaging Menu (https://extensions.gnome.org/extension/519/messaging-menu/) resolved problem.
I see user list and I can login after screen lock.

Comment 2 Fedora End Of Life 2013-09-16 16:31:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 3 Fedora End Of Life 2015-05-29 09:19:02 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 4 Fedora End Of Life 2015-06-29 12:16:20 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.