Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

no Xauth data Solved



On 10/14/2008 05:10 PM, Jarod Wilson wrote:
> On Tue, 2008-10-14 at 16:46 -0400, Jerry Feldman wrote:
>  =20
>> Brendan wrote:
>>    =20
>>>>>>> debug1: Unspecified GSS failure.  Minor code may provide more
>>>>>>> information
>>>>>>> No credentials cache found
>>>>>>>
>>>>>>> debug1: Unspecified GSS failure.  Minor code may provide more
>>>>>>> information
>>>>>>>          =20
>>>>>>>              =20
>>> Comment out the GSS stuff in your /etc/ssh/ssh*_config files on clien=
t and=20
>>> server.
>>>  =20
>>>      =20
>> Agreed, but that is just a red herring and has nothing to do with the
>> specific issue. The problem occurs after ssh authentication and during=

>> the X authentication.
>>    =20
>
> Haven't entirely been paying attention to the whole thread, but perhaps=

> xorg-x11-xauth isn't installed on the ia64 end?
>  =20
I was able to run a number of experiments.
First, it has nothing to do with ssh.
It is specifically a permission issue.
I was able to log out of the console. This removed the=20
var/run/auth-cookie-XXIIWBJU-for-gaf. I then logged into the server from =

my (ugh) Windows XP box with Exceed (X server) and putty. I then=20
performed and 'ssh -X'. There was absolutely no delay. From the log and=20
running xauth, it appears that GDM is locking the auth cookie.
[gaf at boslc01 ~]$ /usr/bin/xauth list
/usr/bin/xauth:  timeout in locking authority file=20
/var/run/gdm/auth-cookie-XXIIWBJU-for-gaf

After googling on this specific message I found a solution:
1. the permission for /var/run/gdm on F9 IA64 is:
drwxr-xr-t  2 root gdm  4096 2008-10-16 08:20

2. After changing the permission to
drwxrwxrwt  2 root gdm 4096 2008-10-16 10:14 gdm
Xauth was able to successfully establish the lock.
I checked my home Fedora9 system and it was set to drwxrwxrwt.

So, I think the problem is with the Fedora 9 installation on IA64.
If I have some time, I might file a bugzilla on it, but F10 is close to=20
release.



--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846










BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org