Bug 117718 - Gnome-screensaver isnt themed
Summary: Gnome-screensaver isnt themed
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: RC 1
Hardware: Other All
: P3 - Medium : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 07:15 UTC by Jonathan Arsenault
Modified: 2006-02-06 01:29 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Arsenault 2005-09-19 07:15:36 UTC 
gnome-screensaver screen asking for a password after leaving the computer alone
for a while isnt themed and look weird
Comment 1 Rodrigo Moya 2005-09-19 11:19:28 UTC 
Could you attach a screenshot please? It is indeed themed in all the machines
I've tested.
Comment 2 Jonathan Arsenault 2005-09-19 17:23:22 UTC 
Yeah your right tested almost all theme included for gnome in SuSE they all work
fine except for the crystalsphere svg theme , instead of a small box in the
middle of the screen with comp name etc the whole screen get filled with with
the default windows filling with randomlly white of black stripe at the bottom
or top of the screen. Really look weird. sorry about screenshot but in gnome i
never figured out how to take pic of both the menu and the screensaver. Hey now
that i changed back and forth between theme the name of the box now appear but
still same fill out the whole screen behavior.
Comment 3 JP Rosevear 2005-09-22 20:10:30 UTC 
Gary, Stanislav - I'm thinking we should drop CrystalSpheres as its old and
unmaintained.  Perhaps we could package gnome-themes-extras instead.

Need to make sure we fall back to the default theme (Industrial) in our case though.
Comment 4 Jonathan Arsenault 2006-02-06 01:29:54 UTC 
ok well will just be closing this as a wontfix bug.