After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157147 - per display registration fails if DISPLAY env is not complete
per display registration fails if DISPLAY env is not complete
Status: RESOLVED OBSOLETE
Product: gnome-terminal
Classification: Core
Component: general
git master
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-02 17:35 UTC by Balamurali Viswanathan
Modified: 2008-09-25 18:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Balamurali Viswanathan 2004-11-02 17:35:08 UTC 
In a xterm if I set DISPLAY=:0 

* I am able to start 2 instances of gedit
* When I start 2 instances of gnome-terminal then 2 process of gnome-terminal is
running.

The above is not the case when the DISPLAY is set to :0.0
Comment 1 Michael Meeks 2004-11-16 12:41:29 UTC 
this is a gedit bug then - it's necessary to canonicalise the display first I
think; and/or there may be a libbonobui method that does that for you - I forget
the details.
Comment 2 Paolo Maggi 2005-02-01 11:27:10 UTC 
I have fixed this problem in gedit, but I think it is still present in
gnome-terminal.
So I'm going to change the product to gnome-terminal.
Comment 3 Kjartan Maraas 2005-09-19 11:13:17 UTC 
Paolo, could you comment on how you fixed it?
Comment 4 Christian Persch 2008-09-25 18:34:50 UTC 
This is obsolete now that we use dbus for the single instance code, with one instance per bus not one per display. 
I checked and we do use the same method as gedit to get from a display name in the client to the GdkDisplay in the factory process.
Closing.