Red Hat Bugzilla – Bug 472596
2nd screen doesn't get locked if anything is running on it
Last modified: 2015-01-14 18:22:06 EST
Description of problem:
The 2nd display on a dual-head ppc64 box doesn't get locked when gnome-screensaver kicks in if an application is running on it (okay, only know it happens for sure w/firefox). The 2nd display goes black for a moment, then lights back up w/the browser showing. Wiggling the mouse brings up the unlock dialog on the 1st display, while the browser continues to show. Didn't try clicking in the browser, but I can definitely scroll the browser window up and down while things are supposedly locked.
Version-Release number of selected component (if applicable):
Full-screen firefox on the 2nd display, lock the screen.
Radeon x1650 Pro graphics in a YDL PowerStation, if it matters...
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Also on x86_64 with nv driver. FYI this was not the case under rawhide i386 with the propriety nvidia driver.
I'm also seeing this on x86_64 with this video card:
01:00.0 VGA compatible controller: ATI Technologies Inc RV516 [Radeon X1300/X1550 Series]
01:00.1 Display controller: ATI Technologies Inc RV516 [Radeon X1300 Pro] (Secondary)
This is from a recent Dell Optiplex 745, using the radeonhd driver.
If I have an application on the right-side window, such as thunderbird, it's still completely usable (thus screen locking isn't very effective). As a workaround, I can lock the screen with no application on the right side, and I'll just get what seems to be a useless blank desktop (you can still see my wallpaper, though). Note: I just tested, and the desktop right-and-left hotkeys don't work when locked.
Note that somewhere in the course of getting my F10 machine up and running, something must have 'fixed' this issue - I can't get it to repeat now.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.