Bug 707109

Summary:	Cannot create launcher on Display :0.1
Product:	Red Hat Enterprise Linux 6	Reporter:	Dirk Gfroerer <dirk.gfroerer>
Component:	gnome-panel	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:22:43 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:

Description Dirk Gfroerer 2011-05-24 05:43:59 UTC

Description of problem:
I do have a dual head set up. Right monitor being my primary monitor. Left being my secondary monitor. I'm running "separate X Servers" for each of them. So the right one is :0.0 the left one is :0.1. Whenever I try to create an application launcher on the left monitor, the launcher is created on the right monitor. Create Folder and Create Document work as expected.

Version-Release number of selected component (if applicable):
metacity-2.28.0-20.el6.x86_64

How reproducible:
every time

Steps to Reproduce:
1. Create a dual head set up with different X Servers.
2. On Display :0.1 right click and select "Create Launcher ..."
3. Enter information requested.
  
Actual results:
Launcher appears on Display :0.0

Expected results:
Launcher is created on Display :0.1

Additional info:
I'm not sure if this is related to this, but this set up seems to have its issues. If I e.g. start virt-manager on display :0.1 a dialog pops up on :0.0 asking for the root password. Not really a problem but just an annoyance.

Comment 2 Dirk Gfroerer 2011-05-24 07:03:06 UTC

Forgot to say this worked fine with RHEL 5.6.

Comment 3 RHEL Program Management 2011-07-06 01:35:21 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Owen Taylor 2011-07-06 16:06:29 UTC

This was mistakenly assigned to metacity - it doesn't sound like it has anything to do with the window manager.

Comment 5 Jan Kurik 2017-12-06 10:22:43 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/