Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235175 - Unable to launch X application after changing the hostname with hostname command line
Summary: Unable to launch X application after changing the hostname with hostname comm...
Alias: None
Product: Fedora
Classification: Fedora
Component: XFree86
Version: 6
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-04 10:13 UTC by Frederic Hornain
Modified: 2018-04-11 16:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-04 13:17:14 UTC

Attachments (Terms of Use)

Description Frederic Hornain 2007-04-04 10:13:45 UTC
Description of problem:
Well, I am unable to launch for instance "system-config-users" after having 
changed the hostname from "localhost" to "my_chosen_hostname" with the command 
line hostname.

Version-Release number of selected component (if applicable):

How reproducible:
Easily if you have a X server on your local machine

Steps to Reproduce:
1. Be connected on an X session with you favorite username.
2. Open a Terminal windows in order to enter command line.
3. do an su - and be connected as root.
4. do a "hostname blablabla" in order to change your hostname from "localhost" 
to "blablabla".
5. run the system-config-user command
6. and finally you should have the following message : See actual result.
Actual results:

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Unable to import modules. Maybe you are not running under X ?

Expected results:

Well, I should see the user-configuration window.

Additional info:

Comment 1 Matěj Cepl 2007-04-04 13:17:14 UTC
Reporter, this is not problem of X, but in your configuration. Nobody is allowed
to run application on your X-server, and that includes root. In order to allow
root to run X applications, you have to allow it explicitly with xhost, for
example by running (as normal user owning X-server):

xhost local:

So, this is not a bug.

Note You need to log in before you can comment on or make changes to this bug.