compiz screensaver flashes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| One Hundred Papercuts |
New
|
Undecided
|
Unassigned | ||
| compiz (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: compiz
I'm running compiz and when the screensaver triggers from inactivity, first it gradually fades the brightness of the screen, then it goes black, then there's a flash of bright light, then it goes back to black. I don't think it should be flashing there. (In the dark it's quite noticeable from the next room.)
Once it goes dark, it should stay dark.
There's a similar problem when the screensaver terminates (when the screen is dark and I hit a key). First, the screen flashes up with nothing on it but the screen background (in my case, a photo from my personal collection). Then a second
later, all the windows appear. I don't think it should show the background without the windows. I think the screen should stay black until it has composed the right screen image.
I'm on an HP dc5150 with an HP LP2465 LCD monitor, running Jaunty i386. I installed the Desktop version, but somehow when I added virtual machine support with apt-get, it zapped the desktop startup sequence, so now I'm not sure exactly what variant of Jaunty is running. compiz 1:0.8.2-0ubuntu8 is installed (from apt-cache policy). My screensaver is set to just "Blank screen" and it triggers in 10 minutes. The Power Management preference for the screensaver is to never put the computer to sleep, and to put the monitor to sleep after 17 minutes. It does not lock the screen when blanking it.
| Travis Watkins (amaranth) wrote | #1 |
| Changed in compiz (Ubuntu): | |
| status: | New → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 346187, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.