Bug 3887

Summary: linuxconf refuses to start under X
Product: [Retired] Red Hat Linux Reporter: pushf
Component: linuxconfAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: pushf
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-09-20 01:48:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description pushf 1999-07-03 14:51:31 UTC
When I am running under X, linuxconf doesn't want to start
properly. I have the following error message:

(root@Fury:~)# linuxconf
Message d'erreur de remadmin :
Message d'erreur de remadmin :Gdk-WARNING **: locale not
supported by C library
Message d'erreur de remadmin :Xlib: connection to ":0.0"
refused by server
Message d'erreur de remadmin :Xlib: Client is not authorized
to connect to Server
Message d'erreur de remadmin :
Message d'erreur de remadmin :Gtk-WARNING **: cannot open
display: :0
remadmin (GUI) sortie anormale

My X server is XFCom_i740 ( Precision Insight ).

Thank for helping me !!!

Comment 1 Michael K. Johnson 1999-07-30 14:48:59 UTC
If this problem is still occurring for you, please tell me how
you are starting X: using xdm, gdm, or kdm?  startx?  xinit?
Are you logging in as root or are you using su?  If you are
using su, are you using "su" or "su -"?  Thanks.

Comment 2 Anonymous 1999-08-27 19:19:59 UTC
I also had this problem.  It turned out to be a networking problem.
It appears that the hostname had gotten changed to that given to the
primary interface.  The solution is to make sure that you have the
same name for your hostname and also for your primary interface in the
hosts file.  If your hostname is still localhost.localdomain, but your
primary interface has another name, you will get this problem. Check
your hostname with hostname, and then change it to the other name to
test whether this is the case for you.

Comment 3 Michael K. Johnson 1999-09-20 01:48:59 UTC
sdhill is right -- thanks for pointing out the context.