[winswitch] Not able to connect to a started xpra

Ronald Sterckx ronald.sterckx at gmail.com
Mon Jun 22 14:19:36 BST 2015


Hi,

I have Ubuntu vivid. My desktop is connected to an Active Directory, 
which might be related.
I have tried "--socket-dir=/tmp" but that didn't help.

"/usr/bin/xpra --daemon=no start :10" seems to work though


Ronald
On 12/06/15 14:26, Antoine Martin wrote:
> On 12/06/15 09:08, Ronald Sterckx wrote:
>> Hi,
>>
>> I try to start xpra on display 10 by issuing
>>
>>> $ xpra start :10
>>> Entering daemon mode; any further errors will be reported to:
>>> /home/INTRA/ronalds/.xpra/:10.log
> (snip)
>>> Traceback (most recent call last):
>>>    File
>>> "/usr/lib/python2.7/dist-packages/xpra/server/gtk_server_base.py",
>>> line 61, in add_listen_socket
>>>      sock.listen(5)
>>>    File "/usr/lib/python2.7/socket.py", line 228, in meth
>>>      return getattr(self._sock,name)(*args)
>>> socket.error: [Errno 22] Invalid argument
> That's a very odd looking error you've got there.
> I am unable to reproduce this on Ubuntu Vivid, or any other distro for
> that matter.
>
> Is your home directory on NFS or something?
> If that's the case, you should be using the "--socket-dir=DIR" option to
> place the xpra sockets outside $HOME.
>
> Cheers
> Antoine
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users




More information about the shifter-users mailing list