User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Build Identifier: installed xpra on fc29 and followed the 'Getting Started' instructions: https://www.xpra.org/trac/wiki/Usage [auser@K10x6 Videos]$ xpra start ssh:192.168.8.122 --start=xterm 2018-11-25 10:20:19,144 Xpra gtk2 client version 2.3.4-r20510 64-bit 2018-11-25 10:20:19,145 running on Linux Fedora 29 Twenty Nine 2018-11-25 10:20:20,078 GStreamer version 1.14.4 for Python 2.7.15 64-bit 2018-11-25 10:20:20,246 OpenGL_accelerate module loaded 2018-11-25 10:20:20,251 Using accelerated ArrayDatatype 2018-11-25 10:20:20,604 OpenGL enabled with AMD TURKS (DRM 2.50.0 / 4.19.2-301.fc29.x86_64, LLVM 7.0.0) auser.8.122's password: 2018-11-25 10:20:21,130 desktop size is 1920x1080 with 1 screen: 2018-11-25 10:20:21,130 :0.0 (508x285 mm - DPI: 96x96) 2018-11-25 10:20:21,130 monitor 1 (1000x550 mm - DPI: 48x49) 2018-11-25 10:20:21,293 keyboard settings: rules=evdev, model=pc105, layout=gb 2018-11-25 10:20:21,559 Error: cannot watch for video device changes without pyinotify: 2018-11-25 10:20:21,560 No module named pyinotify [root@K10x6 F29]# dnf provides pyinotify Last metadata expiration check: 0:57:51 ago on Sun 25 Nov 2018 09:23:02 GMT. python2-inotify-0.9.6-13.fc29.noarch : Monitor filesystem events with Python under Linux Repo : fedora Matched from: Filename : /usr/bin/pyinotify server dsnf install python2-inotify-0.9.6-13.fc29.noarch allows connection to continue to the nextv error. ;-) Reproducible: Always Steps to Reproduce: 1.install xpra-2.3.4-1.fc29 2.xpra start ssh:192.168.8.122 --start=xterm 3. Actual Results: Error: cannot watch for video device changes without pyinotify: xterm-in-a-window fails to appear. Expected Results: xterm running on the remote host should appear in a desktop window. Also had to add python-uinput.x86_64 on the server host to make some more progress to the next error. ;-) [root@k8 F27]# dnf search uinput Last metadata expiration check: 0:25:06 ago on Sun 25 Nov 2018 10:16:16 GMT. ========================================= Name & Summary Matched: uinput ========================================= python-uinput.x86_64 : Pythonic API to the Linux uinput kernel module python3-uinput.x86_64 : Pythonic API to the Linux uinput kernel module [root@k8 F27]# dnf install python-uinput.x86_64 | tee dnf_install_python-uinput
Just to be clear I was running this test on a recent fc29 KDE workstation for the client/desktop and connecting to an existing fc27 installation for the server.
saw existing bug #1583319 - xpra-2.3 results in xpra initialization error: invalid mode 'start' but no idea if this is related. Initial post above sets the scene for getting a fresh installation of xpra to the point where a newby can succesfully complete step1 of "Getting Started" https://www.xpra.org/trac/wiki/Usage However the very next example - which is the general case of xpra start :100 --start=xterm then xpra attach ssh/SERVERUSERNAME@SERVERHOST/100 Still fails. This use case of 'start a service and then connect back later' is the one that I wished to achieve colin ~ $ xpra start :10 --start=xterm Warning: cannot use the system proxy for 'start' subcommand, failed to connect to '/run/xpra/system': [Errno 2] No such file or directory colin ~ $ Entering daemon mode; any further errors will be reported to: /run/user/1000/xpra/:10.log colin ~ $ su - Password: [root@k8 ~]# tail -f /run/user/1000/xpra/:10.log 2018-11-25 10:55:17,288 pulseaudio server started with pid 1992 2018-11-25 10:55:17,812 GStreamer version 1.12.5 for Python 2.7.15 64-bit 2018-11-25 10:55:17,856 D-Bus notification forwarding is available 2018-11-25 10:55:17,886 xpra X11 version 2.2.6-r18970 64-bit 2018-11-25 10:55:17,887 uid=1000 (colin), gid=1000 (colin) 2018-11-25 10:55:17,887 running with pid 1952 on Linux Fedora 27 Twenty Seven 2018-11-25 10:55:17,888 connected to X11 display :10 with 24 bit colors 2018-11-25 10:55:18,130 xpra is ready. 2018-11-25 10:55:28,003 printer forwarding enabled using postscript and pdf 2018-11-25 10:55:28,004 7.8GB of system memory ## It seems the xterm process did start, but no connected window appeared on the requesting client? colin ~ $ ps -aux | grep xterm colin 1952 0.0 1.1 999708 97260 ? S 10:55 0:00 /usr/bin/python2 -s /usr/bin/xpra start :10 --start=xterm --start-via-proxy=no colin 2033 0.0 0.1 180680 9860 ? S 10:55 0:00 xterm I note the argument '--start-via-proxy=no' which has appeared. Unfortunately it seems that I have failed to keep a copy of the startup squawk complaining about failure due to /run/xpra/$UID/$pid/something File does not exist. A web search did find me this: "xpra start with proxy fails / xvfb error" http://xpra.org/trac/ticket/1654 but I have not the experteese to proceed with this. Is there any more I can do to debug this? Thanks for your attention. Colin.
xpra-2.4.2-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-bd2686daa4
xpra-2.4.2-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-de89518dc1
xpra-2.4.2-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-bd2686daa4
xpra-2.4.2-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-de89518dc1
xpra-2.4.2-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
xpra-2.4.2-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.