[winswitch] Not able to connect to a started xpra

Ronald Sterckx ronald.sterckx at gmail.com
Mon Jun 22 16:57:20 BST 2015


> "/usr/bin/xpra --daemon=no start :10" seems to work though
I'll rephrase that.  This does work, I can connect in this case. The log is
> 2015-06-22 17:46:29,387 failed to load the mdns avahi publisher: No 
> module named avahi
> 2015-06-22 17:46:29,387 either fix your installation or use the 
> '--no-mdns' flag
> Xlib:  extension "RANDR" missing on display ":10".
> Xlib:  extension "RANDR" missing on display ":10".
> 2015-06-22 17:46:29,648 server uuid is 02e16d84748a48e9b52bdc02754e98de
> 2015-06-22 17:46:29,759 Printer forwarding cannot be enabled, the PPD 
> file '/usr/share/cups/model/CUPS-PDF.ppd' is missing
> 2015-06-22 17:46:29,785 pulseaudio server started with pid 25721
> 2015-06-22 17:46:29,791 using notification forwarder: 
> DBUSNotificationsForwarder(org.freedesktop.Notifications)
> E: [pulseaudio] pid.c: Daemon already running.
> 2015-06-22 17:46:29,793 xpra server version 0.15.1 (r9664)
> 2015-06-22 17:46:29,793 running with pid 25708
> 2015-06-22 17:46:29,827 Warning: pulseaudio has terminated shortly 
> after startup.
> 2015-06-22 17:46:29,827  Either fix the pulseaudio command line or use 
> the 'pulseaudio=no' option to avoid this warning.
> 2015-06-22 17:46:29,827  usually, only a single pulseaudio instance 
> can be running for each user account, and one may be running already
> 2015-06-22 17:46:29,827 xpra is ready.
> 2015-06-22 17:46:29,893 video encoder 'nvenc4' could not be loaded:
> 2015-06-22 17:46:29,894  No module named pycuda
This does not complain about the socket as it normally does.  This is 
not really a workable solution though.

When I use socket-dir the log file still states:
> 2015-06-22 17:43:06,230  usually, only a single pulseaudio instance 
> can be running for each user account, and one may be running already
> 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
> 2015-06-22 17:43:06,230 xpra is ready.
> 2015-06-22 17:43:06,287 video encoder 'nvenc4' could not be loaded:
> 2015-06-22 17:43:06,288  No module named pycuda
This does complain about the socket and I can't connect.


Ronald

On 22/06/15 17:11, Antoine Martin wrote:
> On 22/06/15 15:19, Ronald Sterckx wrote:
>> Hi,
>>
>> I have Ubuntu vivid. My desktop is connected to an Active Directory,
>> which might be related.
> Possible, I can't imagine why unless you use system authentication
> (auth=sys).
>> I have tried "--socket-dir=/tmp" but that didn't help.
> FYI: You need to use this option for both the server and clients.
>> "/usr/bin/xpra --daemon=no start :10" seems to work though
> Seems to?
> Does "xpra info" work? (specifying socket-dir if appropriate)
>
> Cheers
> Antoine
>>
>> 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
>> _______________________________________________
>> shifter-users mailing list
>> shifter-users at lists.devloop.org.uk
>> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>
> _______________________________________________
> 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