Bug 8579 - X logo doesn't appear consistently in built-in screen saver
Summary: X logo doesn't appear consistently in built-in screen saver
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.0.0
Hardware: x86 (IA32) Linux (All)
: high minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-09 18:10 UTC by Daniel Richard G.
Modified: 2010-11-19 19:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Daniel Richard G. 2006-10-09 18:10:31 UTC
I use the X server's screen saver with blanking disabled, the one that draws 
the big X logo on the screen.

Once the saver starts, the logo (solid white on a black background) appears in 
some cycles, and is gone in others (leaving a completely black screen).

Having the logo intermittently disappear somewhat defeats the purpose of the 
saver's blank/noblank option. I prefer to have the logo appear, as visual 
confirmation that the monitor is on.

Looking at dix/window.c, I notice that the logo's color is randomly chosen to 
be either black or white, with black heavily favored. Is it possible that this 
code has remained unchanged from the days when the screen saver drew a stippled 
background? A black or white logo would be visible in that case, but now that a 
plain black background is used, only white would show. Perhaps the logo should 
be drawn unconditionally in white?
Comment 1 Daniel Stone 2007-02-27 01:33:59 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Jesse Adkins 2010-11-19 19:24:30 UTC
The logo hack screen saver is gone as of git commit bfe9cdd11bcb60cf33dc48136ebee028001a737e. (Oct 20 2010). Marking this as invalid.

If I'm wrong, just reopen this.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.