Bug 532901 - gnome-screensaver does not show password dialog when attempting to unlock screen
Summary: gnome-screensaver does not show password dialog when attempting to unlock screen
Keywords:
Status: CLOSED DUPLICATE of bug 530309
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gnome-screensaver
Version: 5.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-04 09:47 UTC by Huzaifa S. Sidhpurwala
Modified: 2018-10-20 04:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-03 14:35:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
debug output (17.87 KB, text/plain)
2009-11-04 09:48 UTC, Huzaifa S. Sidhpurwala 		no flags Details
View All

Description Huzaifa S. Sidhpurwala 2009-11-04 09:47:53 UTC 
1. upgrade from RHEL 5.3 to RHEL 5.4
2. lock screen 
3. attempt to unlock, no password dialog box

[root@caoconno ~]# uname -r
2.6.18-164.2.1.el5
[root@caoconno ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Client release 5.4 (Tikanga)
[root@caoconno ~]# rpm -q gnome-screensaver
gnome-screensaver-2.16.1-8.el5


You have to kill gnome-screensaver manually for you to get access.
Comment 1 Huzaifa S. Sidhpurwala 2009-11-04 09:48:46 UTC 
Created attachment 367431 [details]
debug output
Comment 2 Huzaifa S. Sidhpurwala 2009-11-04 09:49:35 UTC 
Attached above is the output from 
gnome-screensaver --no-daemon --debug
Comment 4 Andrew Rechenberg 2010-12-21 13:41:08 UTC 
Having the same problem with Fedora 14 x86_64 (pre-upgraded from Fedora 13).  Not sure if I should open a new bug since this bug is related to RHEL.
Comment 5 Ray Strode [halfline] 2011-11-03 14:35:47 UTC 
This bug was addressed some time ago.

*** This bug has been marked as a duplicate of bug 530309 ***
Note You need to log in before you can comment on or make changes to this bug.