On 2019-03-22 1:06 PM, dick balaska wrote:
> On 3/22/19 12:45 PM, Le_Forgeron wrote:
>> Le 22/03/2019 à 16:35, Cousin Ricky a écrit :
>> Are you running in local, directly on the linux pc's keyboard & screen ?
>> (or via a remote connection such as ssh ?)
>>
>> If local, are you running in console or X11 display ?
>>
>> you can disable preview (hence the need to open the X display) via
>> command line switch : -d
>>   as well as ini file: Display=Off
>>
>> 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.
>>
> 
> I don't think it's a cookie file per se, although I don't know what that is.
> I think the crux is "invalid display :0"
> I see this sometimes if I ssh into a box.
> My first test is always to see if xclock works.

It works, but it also spits out "Invalid MIT-MAGIC-COOKIE-1 key" in the 
process.

> I'd try like jr says, "-d"

I don't want to use "-d"; it would defeat the purpose of my automated 
testing scripts.

Post a reply to this message