Ubuntu
gnome-screensaver package

Focus follows mouse after closing screensaver on Compiz

Bug #450021 reported by Fibonacci on 2009-10-13

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	Confirmed	High	Sam Spilsbury

Bug Description

Binary package hint: gnome-screensaver

Just as the title says, right after closing the screensaver, the focus behaviour is changed to FFM, but the focused windows are not raised. That, however, runs contrary to what I have set, which is that click is required to focus.
Needless to say, this behaviour is irritating, as keyboard input to one window might be completely stolen by another by the simple act of moving the mouse away to see what I'm typing.

This bug is not triggered when the screensaver has been running for a very short time. Also, apparently, this only happens under Compiz, not on Metacity.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.24.0-0ubuntu6
ProcEnviron:
PATH=(custom, user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-screensaver
Uname: Linux 2.6.28-15-generic i686

Tags:

Revision history for this message

Fibonacci (fibonacci-prower) wrote on 2009-10-13:

Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-07-02:

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of gnome-screensaver is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

Changed in gnome-screensaver (Ubuntu):
status:	New → Incomplete

Revision history for this message

Juan Sebastián Marulanda (juanchito2006) wrote on 2010-07-04:

Yep, still happens.

Changed in gnome-screensaver (Ubuntu):
status:	Incomplete → New

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-09-03:

Thank you for taking the time to report this bug and helping to make Ubuntu better.You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Do you get the same with latest Lucid packages or in Maverick? Thanks in advance.

Changed in gnome-screensaver (Ubuntu):
status:	New → Incomplete

Revision history for this message

Fibonacci (fibonacci-prower) wrote on 2010-09-06:

Yes.

Changed in gnome-screensaver (Ubuntu):
status:	Incomplete → New

Revision history for this message

Juan Sebastián Marulanda (juanchito2006) wrote on 2010-10-10:

Still happening in Maverick.

Changed in gnome-screensaver (Ubuntu):
status:	New → Confirmed

Revision history for this message

Fibonacci (fibonacci-prower) wrote on 2010-10-11:

Confirmed.

Revision history for this message

Andrey (iloveeclipse) wrote on 2010-11-07:

Still in 10.04...

Revision history for this message

Amir (amiryal) wrote on 2011-01-11:

Temporary workaround: the problem goes away after bringing another window to the front. The problem then reappears the next time around.

Any news on this bug? Does anybody know of a more permanent workaround?

Revision history for this message

Derek (bugs-m8y) wrote on 2011-03-16:

#10

Behaviour appears to be same as
https://bugzilla.mozilla.org/show_bug.cgi?id=631518

FWIW.

Sam Spilsbury (smspillaz) on 2011-03-16

Changed in gnome-screensaver (Ubuntu):
importance:	Undecided → High
assignee:	nobody → Sam "SmSpillaz" Spilsbury (smspillaz)

Revision history for this message

Andrey (iloveeclipse) wrote on 2011-03-16:

#11

Also in 10.10 64 bit...

Revision history for this message

Juha Aatrokoski (jha-kurp) wrote on 2011-07-21:

#12

I ran into this bug on Gentoo. The patch 2 in https://bugzilla.mozilla.org/show_bug.cgi?id=631518 seems to have fixed this. That patch was also used to fix https://bugs.launchpad.net/compiz/+bug/438868 so looks like this bug should be fixed in Ubuntu (at least Lucid and Maverick).

Also, I found a way to consistently reproduce this bug: lock the screen, bring up the password dialog by pressing a key or moving the mouse, wait until it times out and disappears, then bring it up again and enter your password. At least for me this triggered the bug every time with unpatched compiz.