On 2019-03-22 2:43 PM (-4), Le_Forgeron wrote:
> Le 22/03/2019 à 18:09, Cousin Ricky a écrit :
>> On 2019-03-22 12:45 PM (-4), Le_Forgeron wrote:
>>> As you upgraded, it is possible the old cookie remains and is no more
>>> valid for the new server (such cookie is in a file in your home, a
>>> hidden dot file, and is created by the logging process but ONLY if it
>>> does not exist). Basic test: find the cookie file, nuck the cookie file,
>>> disconnect, reconnect.
>> What would be the name of this file?
> Have a look there:
As it turns out, this is one of the pages I found during my searches.
It is way over my head, and I don't know how I can use this info to fix
the damn problem.
> For my system:
> - cookie file is ~/.Xauthority
> - it was created at the day and hour I logged in.
> - it contains a single entry for my display.
> jerome@krynn:~$ xauth list
> krynn/unix:0 MIT-MAGIC-COOKIE-1 c81a816f0a1c24bcc3dce3aed7d8c746
> jerome@krynn:~$ ls -l .Xauthority
> -rw------- 1 jerome jerome 50 mars 22 17:16 .Xauthority
I get the same thing on my system.
> Notice the rights on the file: User only. As stated in first line of
> answer, mess with them and you are in for a party of problems.
> you can use xauth as interactive command interpreter, as in the provided
> link, by calling it without parameter.
> It will show the location, then wait for commands like:
> * list
> * info
> * quit
> good luck.
Post a reply to this message