Bug 194447 - The Fedora Core 5 unlock dialog box is gone
Summary: The Fedora Core 5 unlock dialog box is gone
Keywords:
Status: CLOSED DUPLICATE of bug 193439
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-08 09:06 UTC by Priit Eylandt
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-04 05:46:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.