Bug 1168502

Summary: cannot unlock session
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.1CC: mdomonko, rstrode, vbenes, vrutkovs
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64   
OS: Linux   
Whiteboard:
Fixed In Version: gdm-3.14.2-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 07:13:26 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:
Bug Depends On:    
Bug Blocks: 1205796    
Attachments:
Description Flags
xorg configuration for dummy driver none

Description Vladimir Benes 2014-11-27 07:40:38 UTC 
Description of problem:
after locking screen I cannot unlock anymore on ppc64.

Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-42.el7.ppc64
polkit-0.112-5.el7.ppc64
gnome-settings-daemon-3.8.6.1-12.el7.ppc64

How reproducible:
always

Steps to Reproduce:
0.configure X for dummy driver (see attached xorg.conf)
1.start gdm service
2.start x11vnc
3.log to local session from gdm over vnc
4.lock the screen
5.unlock

Actual results:
wheel still rotating

Expected results:
logged back in

Additional info:
Comment 1 Vladimir Benes 2014-11-27 07:46:13 UTC 
Created attachment 961898 [details]
xorg configuration for dummy driver
Comment 2 Ray Strode [halfline] 2014-12-17 14:48:08 UTC 
can you run

1) # mkdir -p /var/log/journal
2) Edit /etc/gdm/custom.conf and add Enable=true to the [debug] section
3) reboot
4) reproduce
5) post the output of

# journalctl -b -a -l
Comment 9 Vadim Rutkovsky 2015-06-23 16:47:19 UTC 
Verified on x86_64, ppc64, ppc64le and s390x
Comment 12 errata-xmlrpc 2015-11-19 07:13:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2216.html