Subject: Re: After installing YDL 1.2, problems with Xlib: connection to":0.0" refused by server
From: Harold Bolton (bolton@asl.cr.usgs.gov)
Date: Wed Apr 12 2000 - 09:59:11 MDT
Doesn't work for me. Though kppp has wide open permissions and I set what it
is linked to (/usr/bin/consolehelper) open to the world, I still get the
Xlib messages listed at the bottom.
cheers,
-harold
-----Original Message-----
>From: Nathan Hjelm
>you can set the suid bit on kppp to fix that problem, as for the other,
>if you are using x as one user and trying to make a connection to that as
>another user it will not work until you tell x to allow connections from
>other users on the local machine by typing xhost +localhost
>
>On Wed, 12 Apr 2000, Harold Bolton wrote:
>
>> I also get the same message when using kppp as a user. I first get asked
to
>> enter root password and then get the message. If I am logged in in ANY
>> other terminal as root then I (as another user) can use kppp just fine.
I'd
>> like to know how to avoid this minor complication.
>> -harold
>>
>> Harold Bolton
>> Data Collection Center
>> Albuquerque Seismological Laboratory
>> US Geological Survey
>> Building 10002, Kirtland AFB-East
>> Albuquerque, NM 87115-5000
>>
>> Phone: 505 846-5646 (ext 3032 for voice mail)
>> FAX: 505 846-6973
>> E-mail: bolton@asl.cr.usgs.gov
>> -----Original Message-----
>> From: Jim Cole <greyleaf@yggdrasill.net>
>> To: yellowdog-general@lists.yellowdoglinux.com
>> <yellowdog-general@lists.yellowdoglinux.com>
>> Date: Tuesday, April 11, 2000 11:23 PM
>> Subject: Re: After installing YDL 1.2, problems with Xlib: connection
>> to":0.0" refused by server
>>
>>
>> >pac1@tiac.net's bits of Tue, 11 Apr 2000 translated to:
>> >
>> >>regardless of the setting of the suid bit on kppp & kppp I get:
>> >>
>> >>bash-2.03$ kppp&
>> >>[1] 658
>> >>bash-2.03$ Xlib: connection to ":0.0" refused by server
>> >>Xlib: Client is not authorized to connect to Server
>> >>kppp: cannot connect to X server :0
>> >
>> >Sounds like you are trying to run kppp as someone other than the user
>> >that started the X session. Try doing an xhost + in a shell logged in
>> >as the user who started X before doing the kppp. Do a man xhost if you
>> >want to be more restrictive with the access control.
>> >
>> >Jim
>> >
>> >
>>
>
>
This archive was generated by hypermail 2a24 : Sun Apr 23 2000 - 22:14:39 MDT