[fglrx] GL screensaver obscures window to enter password when lock is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xscreensaver (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xscreensaver-gl
Currently running 10.04 i386 RC (fresh install on same hardware), although the problem was also happening on 9.10 i386.
Graphics card is ATI Radeon 4350.
Graphics driver is ATI/AMD proprietary FGLRX.
System is configured to lock when screensaver is active & require password to terminate. Screensaver is also set to activate after 5 minutes of inactivity.
If any GL-based screensaver from xscreensaver-gl 5.10-3ubuntu-4 (such as GLBlur, GLCells, etc.) is selected & is active, when I move mouse/press any key to stop screen saver, I do not see the dialog where I can enter my password. However, if I type my password carefully, it will unlock & display the desktop. If I mis-type my password, it locks & requires either restarting X server and/or rebooting.
With a non-GL screensaver (such as Cosmos), the screensaver clears & the enter password dialog is shown.
Thank you for taking the time to look into this issue!
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xscreensaver-gl 5.10-3ubuntu4
ProcVersionSign
Uname: Linux 2.6.32-
NonfreeKernelMo
Architecture: i386
Date: Sun Apr 25 21:18:57 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xscreensaver
summary: |
- GL screensaver obscures window to enter password when lock is enabled + [fglrx] GL screensaver obscures window to enter password when lock is + enabled |
Changed in xscreensaver (Ubuntu): | |
status: | New → Confirmed |
Today I installed Ubuntu 10.04 RC as a Virtualbox virtual machine. Hardware was quite different--namely a Nvidia Quadro 290 graphics card. The VM was configured with 3D acceleration enabled. er-command --lock tied to a keyboard shortcut) or allowed to start after the defined 5 minute wait. Either way will provide the same result.
With the exact same GL-screensaver, I observed the exact same result: the password window is obscured by the (now "frozen") screensaver graphics.
I forgot to mention originally it does not matter if the screen saver is forced to start (ala gnome-screensav