Button pressed event registered by wrong window

Bug #546583 reported by Hernando Torque
56
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Metacity
Confirmed
Unknown
metacity (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Windows maximized via a double click on their title bars will register the next
mouse button pressed event even if they are not the "target".

Example 1 - Dragging the wrong window:

1.) Open Nautilus (make sure it's not maximized)
2.) Double click on the title bar to maximize it (don't use the window button)
3.) Start gnome-terminal and try to drag it around
4.) You should have dragged Nautilus instead

Example 2 - Closing/minimizing/restoring the wrong window:

1.) Open Nautilus and maximize it (using the window button)
2.) Open gnome-terminal and maximize it (using a double click on the title bar)
3.) Bring Nautilus to front (via Alt+Tab or the window list in the bottom panel)
4.) Click on Nautilus' close/minimize/restore button
5.) You should have closed/minimized/restored gnome-terminal instead

Of course it's not limited to those two programs.

This doesn't happen with compositing/compiz enabled.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 25 02:40:22 2010
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: metacity 1:2.30.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
SourcePackage: metacity
Uname: Linux 2.6.32-19-generic i686

Revision history for this message
Hernando Torque (htorque) wrote :
Doug McMahon (mc3man)
Changed in metacity (Ubuntu):
status: New → Confirmed
Revision history for this message
sojourner (itsmealso2) wrote :

the same on my amd64 sys with nvidia-current and "none" selected for visual effects . If I start compiz the system acts normaly .

Revision history for this message
Hernando Torque (htorque) wrote :

Seems this bug is already known (via https://bugzilla.redhat.com/show_bug.cgi?id=533066):

* https://bugzilla.gnome.org/show_bug.cgi?id=608296 - includes the commit that might be responsible (tested and fixes this bug)
* https://bugzilla.gnome.org/show_bug.cgi?id=608144 - dupe of above
* https://bugzilla.gnome.org/show_bug.cgi?id=600227 - cannot reproduce, but likely connected
* https://bugzilla.gnome.org/show_bug.cgi?id=608139 - cannot reproduce, but likely connected

Linking to bug 608296 as this looks most promising.

Revision history for this message
Hernando Torque (htorque) wrote :

Updated the description: it does happen with Nouveau - I made a mistake during testing. If this is a Metacity bug it will affect all video drivers anyways.

description: updated
Changed in metacity (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
description: updated
summary: - Drags the wrong window
+ Button pressed event registered by wrong window
Changed in metacity:
status: Unknown → New
Changed in metacity:
status: New → Invalid
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Upstream bug has been marked as duplicate of bug https://bugzilla.gnome.org/show_bug.cgi?id=599181

Changed in metacity:
status: Invalid → Unknown
Changed in metacity:
status: Unknown → Confirmed
Revision history for this message
Adam H. Peterson (ahp-byu) wrote :

Why is the importance of this bug marked as low? Several times I've had the wrong window closed when clicking the close-x and ended up killing half a dozen gnome-terminal tabs at once, some running ssh processes into production machines. (When windows are maximized, a close event on one window is at the same mouse location as a close event on most other windows.) Usually, but not always, I'm saved by having long-running processes on remote servers run in a screen session so they survive the lost connection, but it seems to me that a bug that routinely kills the wrong process is more than "low" importance.

Revision history for this message
Adam H. Peterson (ahp-byu) wrote :

Oops. I didn't notice this was marked as a duplicate. I'll be quiet now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.