Bug 194447

Summary: The Fedora Core 5 unlock dialog box is gone
Product: [Fedora] Fedora Reporter: Priit Eylandt <peylandt>
Component: gnome-screensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: jf_saucier, jmccann
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-04 05:46:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Priit Eylandt 2006-06-08 09:06:21 UTC
Description of problem:


Version-Release number of selected component (if applicable): 
gnome-screensaver-2.14-1

Actual results:
The unlocking dialog box looks as gnome default

Expected results:
Fedora Core 5 unlocking dialog box

Additional info:
I have selected Floating Fedora Bubble for screensaver theme. In gConf editor I
have fedoralogo-floaters value there. Other screensaver themes have also the
same Gnome default unlock dialog box

Comment 1 Priit Eylandt 2006-06-08 09:32:05 UTC
Sorry for the typo:
the version is gnome-screensaver-2.14.2-1

Comment 2 Jean-Francois Saucier 2006-06-08 15:18:59 UTC
Just to confirm the bug, I have the same problem with the update yesterday.

I have also made custom theme with custom login box and they all switch to Gnome
default.

Comment 3 Nalin Dahyabhai 2006-06-08 15:38:59 UTC
Duplicate of bug #193439?

Comment 4 Jean-Francois Saucier 2006-06-08 17:09:36 UTC
yeah, it seems to be the same bug

But I don't find the key in gconf-editor...

Comment 5 Priit Eylandt 2006-06-08 17:24:54 UTC
There is the key but it doesn't help like it did for that person

Comment 6 Priit Eylandt 2006-06-08 17:28:18 UTC
gconf-editor->apps->gnome-screensaver->themes

Comment 7 Matthias Clasen 2006-08-04 05:46:14 UTC

*** This bug has been marked as a duplicate of 193439 ***