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 149786 - Running gnome-control-center remotely replaces X resources settings
Running gnome-control-center remotely replaces X resources settings
Status: RESOLVED DUPLICATE of bug 101683
Product: gnome-control-center
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-10 05:11 UTC by Matt Johnston
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matt Johnston 2004-08-10 05:11:27 UTC 
Description of Problem:
When running gnome-control-center from a non-gnome X 
server (ie ssh -X in to a gnome-running box then run gnome-
control-center), the Xresources settings are replaced with 
gnome default Xresources settings.

Steps to reproduce the problem:
1. From a non-gnome X server with customised Xresources 
(xrdb ~/.Xdefaults) settings, ssh -X to the gnome box. 
2. Run gnome-control-center
3. On the local box, run an xterm. It will have the xresources 
settings set by the gnome box.

Actual Results:
The xterm will be white and have a different font.

Expected Results:
The xterm will have the same default settings, as specified in the 
local ~/.Xdefaults file.

How often does this happen? 
Consistently

Additional Information:
Running gnome-control-center remotely may seem strange, I 
was running in to try and find what the gnome font settings 
were for another gnome app run remotely - so it's not that 
unusual a setup.
Comment 1 Sebastien Bacher 2004-11-28 01:41:56 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 101683 ***