Description of problem: $DISPLAY differs according to parent app Version-Release number of selected component (if applicable): gnome-shell-3.6.2-6.fc18.i686 gnome-terminal-3.6.1-1.fc18.i686 nautilus-3.6.3-4.fc18.i686 nautilus-open-terminal-0.19-6.fc18.i686 How reproducible: Always Steps to Reproduce: 1. Open terminal using gnome-shell 2. Open terminal using nautilus' "Open in Terminal" ( package: "nautilus-open-terminal" ) 3. type echo $DISPLAY in each of them Actual results: First shows ":0" and the second ":0.0" Expected results: They should have the same $DISPLAY Additional info: This causes gedit window mismatch: a file opened on gedit via nautilus can't have its tab moved to another gedit window opened via gnome-shell. I suppose this happens to other programs as well. (previously, gedit crashed [1], now it spawns another gedit when one attempts to move the tab ) References: [1] https://bugzilla.redhat.com/show_bug.cgi?id=808789
gedit behaviour, detailed on "Additional info", proves the problem is at a layer of at least nautilus and not below. Namely: 1. open gedit and nautilus via gnome-shell 2. on Nautilus: open /usr/share/doc/fedora-release-18 , click on "GPL" text file 3. "GPL" text file is opened on a new gedit window 4. the tab can't be moved successfully to the gedit opened via gnome-shell. One assumes gedit refuses to accept the moved tab because it has been opened on a gedit window on a "different" $DISPLAY.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
No longer happens at least on Fedora 20 (64 bits) -- bug was reported against Fedora 18 (32 bits).