Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 425070 (CVE-2012-3452) - gnome-screensaver-3.4.2 causing gnome-shell lockups (CVE-2012-3452)
Summary: gnome-screensaver-3.4.2 causing gnome-shell lockups (CVE-2012-3452)
Status: RESOLVED FIXED
Alias: CVE-2012-3452
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-06 15:05 UTC by Harris Landgarten
Modified: 2012-08-06 11:16 UTC (History)
9 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
gnome-screensaver-3.4.1 ebuild with epatch_user enabled (gnome-screensaver-3.4.1.ebuild,1.95 KB, text/plain)
2012-07-07 04:19 UTC, Alexandre Rostovtsev (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harris Landgarten 2012-07-06 15:05:32 UTC
Ever since the upgrade to gnome-screensaver-3.4.2 every time I return to my workstation after several hours, it will not take screens out of DPMS sleep. I can wake the screens up with a HUP of gnome-shell from another computer. This only works sometimes as 2 of my 3 monitors go dim and I have no mouse or keyboard. A second HUP sometimes works and sometimes results in the "Something is wrong" gnome-shell error screen.

I also noticed in the message.log, a few segfaults in mail-notification and 1 time in gnome-settings-daemon that are connected to either the screensaver wake up or the gnome-shell restarts.

I used to have screen wakeup issues with earlier versions of gnome-3. I haven't had any in many many months until the last couple of days. 

I downgraded to 3.4.1 and will see if that fixes the issue and report back when I have more information.
Comment 1 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-06 15:37:19 UTC
I wonder if gdk_screen_get_primary_monitor() is failing for you...

What version of gtk+, gnome-shell, and gnome-desktop do you have? What video card and what driver? Are you using multiple monitors?
Comment 2 Harris Landgarten 2012-07-06 15:56:49 UTC
gtk+-3.4.3-r1
gnome-shell-3.2.2.1

video is nvidia quadro 5000

same bug with nvidia-drivers-295.59 and 302.17

I have 3 1920x1200 monitors. 2 are connected through a matrox triple head to go
so xrandr sees 2 monitors 3840x1200 and 1920x1200

Under nvidia-295.59 I was faking xinerama into 3 1920x1200 but under 302.17 I am not faking xinerama so that doesn't seem to be the issue.

I have lock turned off in screensaver.

I am also set for all monitors to switch on workspace changes.
Comment 3 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-06 18:30:39 UTC
And does downgrading to gnome-screensaver-3.4.1 fix the problem?
Comment 4 Harris Landgarten 2012-07-06 19:00:26 UTC
After 2 lockups yesterday, I changed the timeout to 1 min to see if I could reproduce and maybe see something in a log.

Of course after the screens blanked a minute later, a move of the mouse brought everything back. Then this morning when I moved the mouse the screens would not move out of sleep. If took 2 HUPs and a logout.

It seems the screens or graphics card needs to be left for hours before the bug happens. I downgraded to 4.3.1 earlier today and have it running but I have been working all day and with my 1hr timeout -- no screensaver. Later when I go to dinner it will have a chance to fail but the real test will be tomorrow morning after overnight.
Comment 5 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-06 20:58:05 UTC
It's also possible that you are expiencing bug #401689 (segmentation fault in nome-screensaver-dialog). Check whether /usr/libexec/gnome-screensaver-dialog crashes if you manually run it from the terminal.
Comment 6 Harris Landgarten 2012-07-06 22:52:05 UTC
I have lock turned off so there is no signon dialog so I don't think that's it. I just came back to my computer after 3 hours away and I came right up from DPMS sleep right away. If it does the same tomorrow morning it would point to the new gnome-screensaver as the problem. Any idea of what was changed that could be causing monitors to not turn on?
Comment 7 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-07 03:19:57 UTC
(In reply to comment #6)
> Any idea of what was changed that could be causing monitors to not turn on?

There were only two changes:

* using gdk_screen_get_primary_monitor() to display the panel with the clock only on the primary monitor: http://git.gnome.org/browse/gnome-screensaver/commit/?id=fc6695ecb9023b7049fa0dba91276d39f983425e

* change the way the background is painted on the screen-sized drawing area widget that blocks out your desktop: http://git.gnome.org/browse/gnome-screensaver/commit/?id=43ee32edaddb9b9b9f4b43c47ca73d7b4eea9fae
Comment 8 Harris Landgarten 2012-07-07 03:47:09 UTC
I now have two straight instances of long DPMS monitor sleep and recovery with no issued using 3.4.1 so we can assume the issue is 3.4.2 and not something else.

This is exactly what happens when 3.4.2 fails:

1. moving of the mouse show some hd activity but the monitors never turn on at all.

2. after a HUP to gnome shell from anyone computer, the screens come on fully but a second or 2 later the 3820x1200 TH2G0 monitors go 3/4 dim and I have no mouse or keyboard.

3. after a 2nd HUP to gnome shell, I either have a normal computer or a something went wrong dialog that only shows 1 extension to turn off when many are installed. After the second HUP I have mouse and keyboard to either use the computer or close programs and logoff.

The single 1920x1200 monitor is the primary btw.

What are you suggestions to figure out what is causing the problem?
Comment 9 Harris Landgarten 2012-07-07 04:00:24 UTC
Another thought:

Since I have Lock turned off in screensaver settings there is no dialog. Can you tell if gdk_screen_get_primary_monitor() is ever called if there is no dialog to display of if it is bypassed.

Also given the weird dimming after the HUP on the 3840x1200 display, I suspect the new blanking method is either causing a driver bug or hardware issue of some kind. I don't understand why they are drawing anything. Why not use either DPMS or xrandr to turn the displays off?
Comment 10 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-07 04:19:06 UTC
Created attachment 317464 [details]
gnome-screensaver-3.4.1 ebuild with epatch_user enabled

(In reply to comment #8)
> What are you suggestions to figure out what is causing the problem?

Could you please try applying one of the two patches from git.gnome.org in the 3.4.1 ebuild, see if it causes the symptoms you got in 3.4.2, and then try with the other patch.

The easiest way to do so is as follows: make sure that /usr/local/portage is in PORTDIR_OVERLAY in your /etc/make.conf; copy the attached ebuild to /usr/local/portage/gnome-extra/gnome-screensaver/; run "ebuild gnome-screensaver-3.4.1.ebuild manifest"; copy the patch you want to apply to /etc/portage/patches/gnome-extra/gnome-screensaver-3.4.1/; and emerge -1 =gnome-screensaver-3.4.1.

Neither of the changes in gnome-screensaver-3.4.2 ought have any effect on DPMS. However, I've searched through the upstream gnome bugzilla, and found the following report which seems similar to the symptoms that you described: https://bugzilla.gnome.org/show_bug.cgi?id=668793
Perhaps one of patches that went into gnome-screensaver-3.4.2 had changed the screensaver window timing just enough so that it triggers that bug on your setup.
Comment 11 Chris Smith 2012-07-07 05:09:43 UTC
Same problem here.
Comment 12 Chris Smith 2012-07-07 05:13:39 UTC
(In reply to comment #11)
> Same problem here.

Sort of that is - I get the lockups but only one monitor.
Comment 13 Chris Smith 2012-07-07 05:18:05 UTC
(In reply to comment #3)
> And does downgrading to gnome-screensaver-3.4.1 fix the problem?

In my case downgrading to 3.4.1 solves the issue.
Comment 14 Chris Smith 2012-07-07 05:20:19 UTC
$ emerge --info
Portage 2.2.0_alpha116 (default/linux/amd64/10.0, gcc-4.6.3, glibc-2.15-r2, 3.4.4-gentoo x86_64)
=================================================================
System uname: Linux-3.4.4-gentoo-x86_64-Intel-R-_Core-TM-_i7-2600K_CPU_@_3.40GHz-with-gentoo-2.1
Timestamp of tree: Sat, 07 Jul 2012 04:15:02 +0000
app-shells/bash:          4.2_p29
dev-java/java-config:     2.1.12
dev-lang/python:          2.7.3-r2, 3.2.3-r1
dev-util/cmake:           2.8.8-r3
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.10.5
sys-apps/sandbox:         2.6
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.9.6-r3, 1.10.3, 1.11.5, 1.12.1
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.3
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4.2
sys-devel/make:           3.82-r3
sys-kernel/linux-headers: 3.4 (virtual/os-headers)
sys-libs/glibc:           2.15-r2
Repositories: gentoo tcg-desktop tcg-server mythtv
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -floop-interchange -floop-strip-mine -floop-block"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -floop-interchange -floop-strip-mine -floop-block"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--with-bdeps y"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuild-head preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirror.netcologne.de/gentoo/ http://chi-10g-1-mirror.fastsoft.net/pub/linux/gentoo/gentoo-distfiles/ ftp://chi-10g-1-mirror.fastsoft.net/pub/linux/gentoo/gentoo-distfiles/ ftp://mirrors.rit.edu/gentoo/ ftp://gentoo.cites.uiuc.edu/pub/gentoo/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en_US en"
MAKEOPTS="-j9"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/tcg_desk /usr/local/portage/tcg_server /usr/local/mythtv_portage/Gentoo"
SYNC="rsync://rsync11.us.gentoo.org/gentoo-portage"
USE="X a52 aac aalib acl acpi alsa amd64 amr apache2 audiofile bash-completion berkdb bluetooth bzip2 cairo caps cdaudio cddb cdparanoia cdr cdrdao chm cli consolekit cracklib crypt cups curl cxx dbus designer-plugin djvu dri dts dv dvb dvd dvdr ebook encode exif fam ffmpeg flac fortran gdbm gif gmp gnome gphoto2 gpm gps graphite gstreamer gtk gtk3 iconv icu ieee1394 imagemagick imap imlib ipv6 jack java jpeg jpeg2k kpathsea lame lcms libffi libnotify mad marble midi mmap mmx modules mozilla mp3 mudflap multilib musicbrainz mythtv ncurses network nls nodrm nptl nsplugin nvidia ofx ogg opencl openexr opengl openmp pam pcre pdf png policykit pulseaudio quicktime readline samba sasl scanner sdl semantic-desktop session slp smp sndfile spell sse sse2 ssl subversion svg theora threads tiff tk transparency truetype udev unicode usb v4l vcd vdpau vim-syntax vorbis vpx wav wavpack wmf x264 xattr xcomposite xine xml xorg xscreensaver xv xvid xvmc zlib" ALSA_CARDS="hda-intel hdsp hpet hrtimer rtctimer seqdummy virmidi" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="*" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en_US en" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
Comment 15 Chris Smith 2012-07-07 05:24:15 UTC
With 3.4.2 the system appears to "awake" immediately but the screen is non-responsive. Oddly enough if I login to another terminal and reboot I will immediately get the locked screen with password box after starting X.
Comment 16 Chris Smith 2012-07-07 05:29:16 UTC
Adding that with gnome-screensaver-3.4.2, when I log into another terminal because I can't get back into my X desktop, one processor core is pegged @100% with the gnome-shell process.
Comment 17 Harris Landgarten 2012-07-07 11:26:08 UTC
Starting to sound like we are overrunning a buffer somewhere and corrupting some memory.
Comment 18 Jeff Sweeney 2012-07-09 00:32:03 UTC
Also running gnome-screensaver-3.4.2, with gtk+3.4.3-r1, gnome-shell-3.2.2.1 on only one monitor. Only seems to lockup after leaving for a while - reactivating desktop just after it blanks is fine. Sending HUP from another terminal window triggers redisplay, immediately activates blanking of the display, but moving the mouse once the fade out completes brings back the desktop immediately with no problems. 
When the lockup occurs, the display is turned back on properly, and the top bar with the clock is displaying, and the mouse pointer, but nothing is responsive and the main body of the desktop remains blank. Am going to try downgrade to see if it fixes the problem.
Comment 19 Harris Landgarten 2012-07-09 14:08:59 UTC
The fact that the screensaver works properly when the mouse moves immediately after blanking or soon after but causes the lockup after blank for a while is confirmed by my observations as well. This in all likelihood is somehow related to DPMS timeouts. DPMS goes from standby to suspend to sleep. The defaults seems to be 20min, 30 min, 40mins. I assume these timeouts start after gnome-screensaver fires.

You can also set these DPMS timeouts yourself with xset -s

If the bug is related to DPMS state, it involves a more complex interaction between gnome-screensaver and energy-star. It will be interesting to see if it happens in suspend or only sleep. We know it doesn't happen in standby.
Comment 20 Chris Smith 2012-07-09 14:21:37 UTC
(In reply to comment #19)
> The fact that the screensaver works properly when the mouse moves
> immediately after blanking or soon after but causes the lockup after blank
> for a while is confirmed by my observations as well.

IIRC the bug appears immediately. If I do a <ctrl><alt>l (that's lower case L) to blank the screen I cannot get back in, no waiting required.
Comment 21 Harris Landgarten 2012-07-09 14:27:01 UTC
I don't have lock enabled. Try turning off lock and setting the screensaver to 1 min. When I so this with 3.4.2 the system comes right back. If I leave the system for a few hours I cannot get back in without a HUP to gnome-shell.
Comment 22 Chris Smith 2012-07-09 14:35:59 UTC
(In reply to comment #21)
> I don't have lock enabled. Try turning off lock and setting the screensaver
> to 1 min. When I so this with 3.4.2 the system comes right back. If I leave
> the system for a few hours I cannot get back in without a HUP to gnome-shell.

I do have lock enabled. For now I've reverted to 3.4.1.
Comment 23 Travis Hansen 2012-07-09 21:53:57 UTC
I've also experienced screen locks occuring imediately after login.  I've just downgraded to 3.4.1 and will report back my experience as well.
Comment 24 Juergen Rose 2012-07-10 16:35:40 UTC
I have the same error on two systems, too.
I still can change the console (e.g. CTL-ALT-F1) and can restart gdm.
Comment 25 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-10 16:54:50 UTC
I have package.masked =gnome-extra/gnome-screensaver-3.4.2 since this bug can severely break the desktop for the users that it affects.

However, I still cannot reproduce it, and would appreciate help, particularly from my fellow Gentoo developers, in debugging the issue.
Comment 26 Harris Landgarten 2012-07-10 17:15:45 UTC
Since I don't see this bug reported on other Linux versions which are on 3.4.2, I wonder if the mixed gnome-3.2, 3.4 we are running on testing has anything to do with it. When can we expect the rest of 3.4 to be unmasked?
Comment 27 cyshei 2012-07-10 20:07:31 UTC
I think I hit this bug today after upgrading libdrm from 2.4.33 to 2.4.37… I had been running gnome-screensaver-3.4.2 with since July 5th with no problems until today.  It seems like downgrading either libdrm or gnome-screensaver both fix the problem for me, so I've gone back to gnome-screensaver-3.4.1 for now.  I'm on Sandy Bridge with x11-drivers/xf86-video-intel-2.19.0.
Comment 28 Travis Hansen 2012-07-11 16:49:14 UTC
OK, I've done a bit of testing and here are my results:

3.4.1 - Works fine
3.4.1 + http://git.gnome.org/browse/gnome-screensaver/commit/?id=fc6695ecb9023b7049fa0dba91276d39f983425e - Works even better

Adding http://git.gnome.org/browse/gnome-screensaver/commit/?id=43ee32edaddb9b9b9f4b43c47ca73d7b4eea9fae both by itself and with the patch above introduces weirdness but I have not been able to reproduce the 100% cpu behavior with it.

Weirdness = 
 * Instead of a black secondary screen I get semi responsive windows.  For example gnome-terminal has responsive tabs, but I cannot type/interact with the actual terminals (ctrl-c, running commands, etc).
 * I don't *see* the actual unlock box.  I can type in my password and both screens will then work, but the password entry box/screen is simply all black.

For my own setup I'm sticking with 3.4.1 + http://git.gnome.org/browse/gnome-screensaver/commit/?id=fc6695ecb9023b7049fa0dba91276d39f983425e

If those are really the only 2 patches/changes between 3.4.{1,2} then I'm at a loss.  If we find any other patches let me know and I'll test them out as well.
Comment 29 Doug Goldstein (RETIRED) gentoo-dev 2012-07-12 01:58:06 UTC
I've masked 3.4.2 since the GNOME team told me on IRC it should have already been masked. In addition, I've committed the ebuild supplied here to use epatch_user so you can put patches in:

/etc/portage/patches/gnome-extra/gnome-screensaver/ to make it easier to test. They must end in .patch.
Comment 30 Harris Landgarten 2012-07-12 02:07:52 UTC
I unmasked the rest of gnome-3.4 and installed gnome-screensaver-3.4.2. I activated the screensaver the ctrl-alt L and immediately locked up with large black boxes on 2 of my 3 monitors but not centered or completely covering any of them. A HUP to gnome-shell still left the black boxes partially obscuring the screen and I was still locked out. The only way to get back control was to kill gnome-screensaver and then HUP gnome-shell. It seems evident that the patch that changes the way to screen is overdrawn is the problem. Somehow the package was removed from package-mask. I suggest you put it back.
Comment 31 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-12 18:36:03 UTC
(In reply to comment #29)
(In reply to comment #30)

Chainsaw's fault: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/package.mask?r1=1.13949&r2=1.13950
Comment 32 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-15 22:16:00 UTC
Should be fixed now. Travis, thanks a lot for testing which commit is the one that causes unlock problems.

Note that some Arch Linux users had also reported that commit 43ee32ed is at fault (https://bugzilla.gnome.org/show_bug.cgi?id=679441), and that gnome-screensaver-3.4.3 (recently released) had reverted the wrong commit and is still broken. So we will not be adding 3.4.3 to portage.

>*gnome-screensaver-3.4.2-r1 (15 Jul 2012)
>
>  15 Jul 2012; Alexandre Rostovtsev <tetromino@gentoo.org>
>  -gnome-screensaver-3.4.2.ebuild, +gnome-screensaver-3.4.2-r1.ebuild,
>  +files/gnome-screensaver-3.4.2-gtkrc.patch:
>  Fix screen lock problems on multi-monitor setups (bug #425070, thanks to
>  Travis Hansen for tracking down the problematic commit) and remove broken
>  3.4.2 version.
Comment 33 Travis Hansen 2012-07-16 14:44:23 UTC
The patch being applied in portage now is the one that gave me trouble :(

http://git.gnome.org/browse/gnome-screensaver/commit/?id=fc6695ecb9023b7049fa0dba91276d39f983425e

Is the 'good' one (at least for me).  So perhaps upstream did revert the proper commit?
Comment 34 Chris Smith 2012-07-16 14:48:24 UTC
(In reply to comment #32)
> Should be fixed now. Travis, thanks a lot for testing which commit is the
> one that causes unlock problems.

gnome-screensaver-3.4.2-r1 fixes it for me (but I'm not running multiple monitors)
Comment 35 Travis Hansen 2012-07-16 14:52:47 UTC
(In reply to comment #34)
> gnome-screensaver-3.4.2-r1 fixes it for me (but I'm not running multiple
> monitors)

I guess I'll run with -r1 for a while and see how it goes.
Comment 36 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-16 15:18:21 UTC
(In reply to comment #33)
> The patch being applied in portage now is the one that gave me trouble :(

I am not applying it, I am *reverting* it :)

Notice the "-R" argument to epatch.
Comment 37 Harris Landgarten 2012-07-16 16:08:51 UTC
I can confirm the 3.4.2-r1 works properly for me on my 3 monitors. All blanks and comes back after overnight. Ctrl-Alt-L blanks and locks the screens but the unlock dialog appears on the not primary monitor. This doesn't matter to me.
Comment 38 Travis Hansen 2012-07-16 16:23:51 UTC
(In reply to comment #36)
> 
> I am not applying it, I am *reverting* it :)
> 

Doh! :)
Comment 39 Sean Amoss (RETIRED) gentoo-dev Security 2012-08-06 11:16:19 UTC
Added CVE for tracking purposes.