On 14/02/17 16:16, Berdonces Bonelo, Erik via shifter-users wrote: > Hello, > > I tried again to enroll into the ML and I hope that now it works well.. > > Otherwise, I tried with the flag you pointed out (--dbus-control=no), and I > can connect using xPra client. So that's your first problem solved.
> Hower, I was expecting to use the html flag to connect using the HTML5 client and it doesn’t work (attaching the logs underneath). Your log sample shows that websockify is either not installed or that the version installed is still too old. > As it seems, most of the modules used by xPra can’t be loaded even if they > are installed (dbus, websockify, and all the others are installed). I also > installed the python-dbus, but seems that the error messages haven’t changed > at all…. I am pretty sure that the numerous dbus related warnings you are posing (which have cut out for brevity) are caused by the missing dbus bindings. You can verify that they are installed properly by running: python -c "import dbus" Until that command runs properly, xpra will warn you about missing dbus. > Also, as I can see, the /var/run/xpra folder is not created, so that might be > the problem….. No, if the directory does not exist or if it is impossible to create a socket there, xpra logs this warning and continues. > May it be that the installation is not creating the folder properly? This folder is normally created by tmpfiles.d, but that's probably not functional in Ubuntu 14.04 > xpra start --bind-tcp=0.0.0.0:14500 --html=on --no-daemon --start-child=xterm > --dbus-control=no > 2017-02-14 10:10:23,455 Warning: failed to load the mdns avahi publisher: > 2017-02-14 10:10:23,456 No module named avahi > 2017-02-14 10:10:23,456 either fix your installation or use the 'mdns=no' > option Install the "python-avahi" bindings, or use "mdns=no" > 2017-02-14 10:10:24,237 Error: cannot import websockify connection handler: > 2017-02-14 10:10:24,238 cannot import name WebSocketRequestHandler > 2017-02-14 10:10:24,238 the html server will not be available That's what you need to fix to get the html5 client running. (..) > Warning: failed to import GStreamer: > GStreamer 1.0: Namespace Gst not available > GStreamer 0.10: No module named pygst > 2017-02-14 10:10:24,749 Error: failed to query sound subsystem: > 2017-02-14 10:10:24,750 query did not return any data Install the python gstreamer bindings to avoid this warning. (..) Cheers Antoine > > Thanks a lot for your time! > > Best regards, > > Erik Berdonces > > > On Feb 13, 2017, at 3:24 PM, Berdonces Bonelo, Erik > <[email protected]<mailto:[email protected]>> > wrote: > > Sending again because the attached file is too big. > It can be found uploaded in OneDrive in this link: > https://1drv.ms/u/s!Ar0lgicIauUbhOQEbXldgJy5H-BMbg > > > > Begin forwarded message: > > From: "Berdonces Bonelo, Erik" > <[email protected]<mailto:[email protected]>> > Subject: Re: HTML start-desktop crash > Date: February 13, 2017 at 1:44:44 PM GMT+1 > To: > [email protected]<mailto:[email protected]> > > Hi again, > > I’m sorry but I’m not receiving any of your mails in my mailbox. I have to go > to the ML archives an read the answers there. > > When I meant it doesn’t work is that it throws exactly the same error. And > I’m not using any funny or strange configuration. It’s just a plain Ubuntu > 14.04 server installed with default configuration, just install everything, > enable SSH, and install xPra using the remote winswitch repo. 0.15.10-1 works > as expected, but any version after this, throws the errors that I sent in the > previous message. > > So procedure to reproduce: > > 1. Install Ubuntu Server x64 14.04 in VirtualBox (running in MacOS) or any > server (I have already tried in both). Simple settings, just enabling SSH > server to remote connect and no interface or anything needed. If you want you > can install SSH manually later on yourself, but this doesn’t affect the > result. No NFS, nothing strange, just a plain installation of ubuntu. > > 2. Update the packages and install xTerm:`sudo apt-get update && apt-get > upgrade -y && apt-get install xterm` > > 3. Install xPra (via winswitch or deb packages): > 3.1Follow the instructions in > https://winswitch.org/downloads/debian-repository.html?dist_select=trusty for > trusty (14.04). > 3.2 I also tried the alternative alternative installing with the deb packages > manually from http://xpra.org/dists/trusty/main/binary-amd64/ with dpkg and > apt-get install -f (both procedures 3.1 and 3.2 result in the same error > later on). I made sure to install websockify, python-xxhash, python-reencode, > ffmpeg-xpra when installing deb packages manually. Usually I use the > winswitch PPA repo as it’s much easier. > > Xpra gets installed with version 1.0.3: > > sturgelose@gilgamesh:~$ xpra --version > xpra v1.0.3-r15051 > > 4. Add user ubuntu to Xpra group `sudo usermod -a -G Xpra ubuntu` to avoid > problems. > > 5. Execute `xpra start --bind-tcp=0.0.0.0:14500 --start-child=xterm` (just > start a screen with xterm). There is nothing running in port 14500. You can > also try with different ports, and will result the same problems. Also tried > with `--html=on` option with the HTML5 client, it will happen exactly the > same. And I tried different computers as clients. > > > If the command in 5. is ran as default non root user (ubuntu user), which is > part of the Xpra group (added in 4.), the server doesn’t start and the daemon > ends (mostly the error I sent in previous messages): > 2017-02-13 09:46:02,017 Error: failed to create socket > '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: > '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket > /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > > If run the command (5.) as root user (something I’d like to avoid doing), the > socket connects, but then when connecting from the client, it says it can’t > find bus package (and other packages), which is installed… still you can try > to connect a client but the dbus error will kill the process. > > _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed > _XSERVTransMakeAllCOTSServerListeners: server already running > Initializing built-in extension Generic Event Extension > Initializing built-in extension SHAPE > Initializing built-in extension MIT-SHM > Initializing built-in extension XInputExtension > Initializing built-in extension XTEST > Initializing built-in extension BIG-REQUESTS > Initializing built-in extension SYNC > Initializing built-in extension XKEYBOARD > Initializing built-in extension XC-MISC > Initializing built-in extension SECURITY > Initializing built-in extension XINERAMA > Initializing built-in extension XFIXES > Initializing built-in extension RENDER > Initializing built-in extension RANDR > Initializing built-in extension COMPOSITE > Initializing built-in extension DAMAGE > Initializing built-in extension MIT-SCREEN-SAVER > Initializing built-in extension DOUBLE-BUFFER > Initializing built-in extension RECORD > Initializing built-in extension DPMS > Initializing built-in extension Present > Initializing built-in extension DRI3 > Initializing built-in extension X-Resource > Initializing built-in extension XVideo > Initializing built-in extension XVideo-MotionCompensation > Initializing built-in extension SELinux > Initializing built-in extension GLX > [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing > from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing > from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing > from list! > Using display number provided by Xvfb: :1 > Xlib: extension "RANDR" missing on display ":1". > Xlib: extension "RANDR" missing on display ":1". > /home/sturgelose/.xpra/gilgamesh-1 is not responding, waiting for it to > timeout before clearing it..... > 2017-02-13 13:10:02,461 created unix domain socket: > /home/sturgelose/.xpra/gilgamesh-1 > 2017-02-13 13:10:02,462 Warning: failed to create socket directory > '/var/run/xpra' > 2017-02-13 13:10:02,463 [Errno 13] Permission denied: '/var/run/xpra' > 2017-02-13 13:10:02,463 Warning: cannot create socket > '/var/run/xpra/gilgamesh-1' > 2017-02-13 13:10:02,464 [Errno 2] No such file or directory > 2017-02-13 13:10:02,465 /var/run/xpra does not exist > 2017-02-13 13:10:02,465 user 'sturgelose' is a member of groups: adm, cdrom, > sudo, dip, plugdev, lpadmin, sambashare, xpra > 2017-02-13 13:10:02,551 Warning: menu forwarding is disabled: > 2017-02-13 13:10:02,552 cannot load dbus helper: No module named dbus > 2017-02-13 13:10:02,932 Warning: libvpx ABI version 5 is too old: > 2017-02-13 13:10:02,932 disabling YUV444P support with VP9 > 2017-02-13 13:10:03,028 Warning: failed to load the mdns avahi publisher: > 2017-02-13 13:10:03,029 No module named avahi > 2017-02-13 13:10:03,029 either fix your installation or use the 'mdns=no' > option > 2017-02-13 13:10:03,035 Warning: no X11 RandR support on :1 > 2017-02-13 13:10:03,953 Error: cannot import websockify connection handler: > 2017-02-13 13:10:03,953 cannot import name WebSocketRequestHandler > 2017-02-13 13:10:03,954 the html server will not be available > 2017-02-13 13:10:04,036 Error: failed to import the virtual video module: > 2017-02-13 13:10:04,037 No module named _dbus_bindings > 2017-02-13 13:10:04,051 pulseaudio server started with pid 1349 > Warning: failed to import GStreamer: > GStreamer 1.0: Namespace Gst not available > GStreamer 0.10: No module named pygst > 2017-02-13 13:10:04,496 Error: failed to query sound subsystem: > 2017-02-13 13:10:04,497 query did not return any data > 2017-02-13 13:10:04,499 Warning: failed to load or register our dbus > notifications forwarder: > 2017-02-13 13:10:04,499 No module named dbus.service > 2017-02-13 13:10:04,499 if you do not have a dedicated dbus session for this > xpra instance, > 2017-02-13 13:10:04,500 use the 'notifications=no' option > 2017-02-13 13:10:04,501 Warning: cannot load dbus helper: > 2017-02-13 13:10:04,502 No module named dbus > 2017-02-13 13:10:04,510 Warning: cannot load dbus server: > 2017-02-13 13:10:04,511 No module named dbus > 2017-02-13 13:10:04,517 started command 'xterm' with pid 1370 > 2017-02-13 13:10:04,518 xpra X11 version 1.0.3-r15051 64-bit > 2017-02-13 13:10:04,519 uid=1000 (sturgelose), gid=1000 (sturgelose) > 2017-02-13 13:10:04,519 running with pid 1298 on Linux Ubuntu 14.04 trusty > 2017-02-13 13:10:04,520 connected to X11 display :1 > 2017-02-13 13:10:04,632 xpra is ready. > 2017-02-13 13:10:04,635 2.0GB of system memory > 2017-02-13 13:10:11,299 New tcp connection received from 130.149.223.41:50452 > 2017-02-13 13:10:11,302 Warning: client expects a challenge but this > connection is unauthenticated > 2017-02-13 13:10:11,319 Handshake complete; enabling connection > 2017-02-13 13:10:11,424 Warning: xxhash python bindings not found > 2017-02-13 13:10:11,425 no scrolling detection > 2017-02-13 13:10:11,438 server error processing new connection from > Protocol(tcp socket: 130.149.223.55:14500 <- 130.149.223.41:50452): No module > named dbus > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line > 893, in _process_hello > self.hello_oked(proto, packet, c, auth_caps) > File "/usr/lib/python2.7/dist-packages/xpra/server/server_base.py", line > 1115, in hello_oked > self.default_speed, self.default_min_speed) > File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 357, in > __init__ > self.dbus_server = dbus_exception_wrap(make_dbus_server, "setting up > client dbus instance") > File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_common.py", > line 12, in dbus_exception_wrap > v = fn() > File "/usr/lib/python2.7/dist-packages/xpra/server/source.py", line 355, in > make_dbus_server > from xpra.server.dbus.dbus_source import DBUS_Source > File "/usr/lib/python2.7/dist-packages/xpra/server/dbus/dbus_source.py", > line 7, in <module> > from xpra.dbus.helper import dbus_to_native > File "/usr/lib/python2.7/dist-packages/xpra/dbus/helper.py", line 7, in > <module> > import dbus > ImportError: No module named dbus > 2017-02-13 13:10:11,444 Disconnecting client 130.149.223.41:50452: > 2017-02-13 13:10:11,445 server error (error accepting new connection) > > This happens with any xPra 1.X version. I tried downgrading Xpra to 0.15.10 > with Ubuntu 14.04 and works like a charm. Also, try the whole same procedure > in Ubuntu 16.04 and it works as expected (no errors nor warnings). > > In the client I only have one screen (disconnected the second one and > rebooted even). I tried with other computers as clients and it’s just the > same. The problem is in the xPra server. > > I attach as well an export of the server configuration done with xPra. > <server_xpra_config.zip> > > I can’t provide more information from the session, because directly the > session doesn’t start! So, there is nothing to do with the encoding or > whatsoever, it’s just Xpra not loading any of its dependencies! > > I’m really not doing anything strange, and I’m totally able to use xPra 1.0.3 > in ubuntu 16.04, using exactly the same steps, or Xpra 0.15.10 in ubuntu > 14.04. So, there is something wrong with 1.X versions. > > I hope this time I have redacted everything properly and added all the > details... > > > On Feb 13, 2017, at 12:19 PM, Berdonces Bonelo, Erik > <[email protected]<mailto:[email protected]>> > wrote: > > Hello, > > As a small update, I’ve been trying with different versions of xPra, and > seems that all the 1.X versions do not work with Ubuntu 14.04 LTS. The latest > version compatible with ubuntu 14.04 is 0.15.10-1 of Xpra. > > Best regards, > > Erik Berdonces > > On Feb 13, 2017, at 10:51 AM, Berdonces Bonelo, Erik > <[email protected]<mailto:[email protected]>> > wrote: > > Hi, > > I’m sending it back to this mail, because seems I got a migration in my inbox > and I didn’t receive the answer back (no worries, I read it in the online > mailman archive), plus I got a new mail address. > > On the desktop size the answers helped a lot, and now I’ve been able to run > it in Ubuntu 16.04 after uninstalling VirtualBox additions and configuring my > screen size. > However, I’ve tried to repeat the same process in Ubuntu 14.04, installing > the latest version from WinSwitch repository and I’m having some troubles. As > it seems it can’t create the socket, even if the .xpra folder gets set a 777 > chmod and ubuntu is part of the Xpra group of users. > > Errors are as it follows: > > ubuntu@machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ xpra start > --bind-tcp=0.0.0.0:14500 --html=on --no-daemon > Initializing built-in extension Generic Event Extension > Initializing built-in extension SHAPE > Initializing built-in extension MIT-SHM > Initializing built-in extension XInputExtension > Initializing built-in extension XTEST > Initializing built-in extension BIG-REQUESTS > Initializing built-in extension SYNC > Initializing built-in extension XKEYBOARD > Initializing built-in extension XC-MISC > Initializing built-in extension SECURITY > Initializing built-in extension XINERAMA > Initializing built-in extension XFIXES > Initializing built-in extension RENDER > Initializing built-in extension RANDR > Initializing built-in extension COMPOSITE > Initializing built-in extension DAMAGE > Initializing built-in extension MIT-SCREEN-SAVER > Initializing built-in extension DOUBLE-BUFFER > Initializing built-in extension RECORD > Initializing built-in extension DPMS > Initializing built-in extension Present > Initializing built-in extension DRI3 > Initializing built-in extension X-Resource > Initializing built-in extension XVideo > Initializing built-in extension XVideo-MotionCompensation > Initializing built-in extension SELinux > Initializing built-in extension GLX > [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, > removing from list! > [dix] Could not init font path element /usr/share/fonts/X11/Type1, removing > from list! > [dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing > from list! > [dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing > from list! > Using display number provided by Xvfb: :0 > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > 2017-02-13 09:46:02,017 Error: failed to create socket > '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0': > 2017-02-13 09:46:02,017 [Errno 1] Operation not permitted: > '/home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0' > xpra initialization error: > failed to create socket > /home/ubuntu/.xpra/machine86ec8863-384b-4baf-af76-aadfbefd4400-0 > 2017-02-13 09:46:02,018 closing TCP socket 0.0.0.0:14500 > 2017-02-13 09:46:02,018 killing xvfb with pid 5842 > ubuntu@machine86ec8863-384b-4baf-af76-aadfbefd4400:~$ umask > 0002 > > This is in a plain Ubuntu Server 14.04 and installing the latest version of > xPra and with default configuration. I can run the command with sudo, but > then, it complains that it misses the dbus, websockify and many other > packages. If I try to install them by hand, it says they are already > installed. So, I’m not sure what’s happening that xPra can’t detect the > dependencies are already installed.. > > These two things were the ones crashing xPra previously as I see (now running > in non-daemon mode seems to keep it running, but still can’t run it in HTML > mode and I get lots of warnings) > > Thanks! > Best regards, > > Erik Berdonces Bonelo > > > On Feb 8, 2017, at 5:42 PM, Berdonces Bonelo, Erik > <[email protected]<mailto:[email protected]>> > wrote: > > Hello, > > I’m trying to run a full desktop (I have tried KDE and Unity so far), in > order to manage remotely a server. > At the moment I have this running as a VM in VirtualBox + VBox Addons in my > computer (I hope it isn’t this interfering somehow…). I’ve been trying with > Ubuntu 14.04, Ubuntu 16.04, Kubuntu 16.04 and CentOS 7. In all of them I’ve > installed the latest release from the Winswitch repository (at the moment > 1.0.2). > > Anyways, whenever I start an xpra session, either if I start it from the > client or HTML5 client, the transmitted desktop is a window that is much > larger than my actual physical screen, and I can’t even resize it down. I’ve > tried with the –desktop-scaling option, but it has no effect. > > Also, I’ve tried to use different desktops (kde, gnome and unity), and to > disconnect my physical second screen from my laptop. If I start a simple > program as xterm, there are no problems, it’s the proper size. However, doing > so with a desktop, it just won’t work. > > Any suggestions on this? I’ve gone through all the xpra manual, but I might > have overlooked a setting. Otherwise I don’t know if it can be a bug maybe… > > Thanks a lot, and of course, thanks a lot for your great work and for this > tool! > > Best regards, > > Erik berdonces > > > > > > _______________________________________________ > shifter-users mailing list > [email protected] > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ shifter-users mailing list [email protected] http://lists.devloop.org.uk/mailman/listinfo/shifter-users
