Bug 469279

Summary:	window ops menu opens on the other screen of dual-head setup
Product:	[Fedora] Fedora	Reporter:	Charles R. Anderson <cra>
Component:	metacity	Assignee:	Søren Sandmann Pedersen <sandmann>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	kem, otaylor, sandmann
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-11-16 22:41:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	438944

Description Charles R. Anderson 2008-10-31 01:48:26 UTC

Description of problem:

I have a dual-head setup.  Clicking on the window ops menu on windows on the right screen causes the window ops menu to show up on the left screen, detached from the parent window and floating by itself, usually at the far right edge of the left screen.  Clicking this menu on windows on the left screen works normally.

Version-Release number of selected component (if applicable):
metacity-2.24.0-2.fc10.i386

How reproducible:
always

Steps to Reproduce:
1. configure dual-head
2. open a window on each screen
3. try clicking the window ops menu on each window
  
Actual results:
Window ops menu (minimize, maximize, move, resize, etc.) shows up on the other screen where the window isn't.  This only happens on windows that are on one of two the screens.

Expected results:
Window ops menu should appear attached to the parent window frame.

Comment 1 Bug Zapper 2008-11-26 04:31:35 UTC

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Owen Taylor 2009-11-16 21:25:59 UTC

This is very odd - is it still happening with F11 or F12?

I don't see any code changes that would fix this, but I don't see any duplicate reports either here or upstream which I would expect if this is a general issue.

Comment 3 Charles R. Anderson 2009-11-16 22:29:05 UTC

I haven't seen this in a long time on F11.  I'd say just close it.