From kaefert at gmail.com Tue Jun 5 23:16:07 2018 From: kaefert at gmail.com (=?UTF-8?Q?Thomas_K=C3=A4fer?=) Date: Wed, 6 Jun 2018 00:16:07 +0200 Subject: [winswitch] trying to get started with xpra Message-ID: Hey there! Years ago I used parti + xpra and since I have a similar need again now I wanted to use xpra again. So I installed xpra through my repositories (Linux Mint 18.3 ~ Ubuntu 16.04) which gave me: xpra 0.15.8+dfsg-1 Sadly none of the most basic tutorials seem to work. $ xpra start :100 --start-child=gnome-terminal keeps running, but results in this logfile: $ cat .xpra/:100.log /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server 2018-06-05 23:45:20,196 2018-06-05 23:45:20,196 Xvfb command has terminated! xpra cannot continue 2018-06-05 23:45:20,196 Trying to attach to the still running xpra start process gives: $ xpra attach 2018-06-05 23:54:40,847 xpra gtk2 client version 0.15.8 (r11211) The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 288 error_code 2 request_code 154 minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I think I remember that in the old times one needed to restart the system after installing before having it work as it should. I tried that. Didn't help. I found this link which seems to suggest that the server part only works using a root account: https://github.com/dnschneid/crouton/issues/2676 So I tried that, which instead gave this log: $ cat .xpra/:100.log X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu Current Operating System: Linux RID04689-N550JV 4.15.0-22-generic #24~16.04.1-Ubuntu SMP Fri May 18 09:46:31 UTC 2018 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=af827427-05e7-4a3b-8ddb-03e9aa5ae267 ro quiet splash vt.handoff=7 Build Date: 13 October 2017 01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/home/kaefert/.xpra/Xorg.:100.log", Time: Tue Jun 5 23:59:00 2018 (++) Using config file: "/etc/xpra/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" 2018-06-05 23:59:00,998 Warning: zlib is the only compressor enabled 2018-06-05 23:59:00,999 install and enable lzo or lz4 support for better performance 2018-06-05 23:59:00,999 Warning: 'rencode' packet encoder not found 2018-06-05 23:59:00,999 the other packet encoders are much slower 2018-06-05 23:59:00,999 server uuid is 26a9c4d0426b41c385acc3976739cdf8 2018-06-05 23:59:01,141 pulseaudio server started with pid 23259 W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). E: [autospawn] core-util.c: Home directory not accessible: Permission denied W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock 2018-06-05 23:59:01,150 using notification forwarder: DBUSNotificationsForwarder(org.freedesktop.Notifications) 2018-06-05 23:59:01,169 started child 'gnome-terminal' with pid 23282 2018-06-05 23:59:01,170 xpra server version 0.15.8 (r11211) 2018-06-05 23:59:01,170 running with pid 23242 2018-06-05 23:59:01,170 Warning: pulseaudio has terminated shortly after startup. 2018-06-05 23:59:01,170 Either fix the pulseaudio command line or use the 'pulseaudio=no' option to avoid this warning. 2018-06-05 23:59:01,170 usually, only a single pulseaudio instance can be running for each user account, and one may be running already 2018-06-05 23:59:01,260 you may want to disable mdns support to avoid this 2018-06-05 23:59:01,264 xpra is ready. Xlib: extension "GLX" missing on display ":100". 2018-06-05 23:59:01,512 child 'gnome-terminal' with pid 23282 has terminated Connecting to this server ran as root using $ xpra attach gives the exact same output as before (and opens no gnome-terminal) Can somebody help me? Is the xpra version 0.15.8+dfsg-1 that I got from the Linux Mint18.3/Ubuntu16.04 repository broken? Or is xpra not usable on current linux desktop systems in general? What do you suggest would be the easiest way to get it functional, if thats possible on this system? Thank you, Kind regards, Thomas K. From antoine at nagafix.co.uk Wed Jun 6 05:57:21 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 6 Jun 2018 11:57:21 +0700 Subject: [winswitch] trying to get started with xpra In-Reply-To: References: Message-ID: On 06/06/18 05:16, Thomas K?fer via shifter-users wrote: > Hey there! > > Years ago I used parti + xpra and since I have a similar need again now I > wanted to use xpra again. > > So I installed xpra through my repositories (Linux Mint 18.3 ~ Ubuntu > 16.04) which gave me: > xpra 0.15.8+dfsg-1 > > Sadly none of the most basic tutorials seem to work. > > $ xpra start :100 --start-child=gnome-terminal > keeps running, but results in this logfile: > > $ cat .xpra/:100.log > /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server > 2018-06-05 23:45:20,196 > 2018-06-05 23:45:20,196 Xvfb command has terminated! xpra cannot continue > 2018-06-05 23:45:20,196 > > Trying to attach to the still running xpra start process gives: > $ xpra attach > 2018-06-05 23:54:40,847 xpra gtk2 client version 0.15.8 (r11211) > The program 'Xpra' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadValue (integer parameter out of range for operation)'. (snip) > > I think I remember that in the old times one needed to restart the system > after installing before having it work as it should. I tried that. Didn't > help. Do not use the packages provided by Ubuntu, they are fundamentally broken (as you found out) and dangerous (lots of unfixed serious vulnerabilities), for details see: https://xpra.org/trac/wiki/Packaging/DistributionPackages > I found this link which seems to suggest that the server part only works > using a root account: > https://github.com/dnschneid/crouton/issues/2676 That is definitely false when it comes to xpra. You need root to run Xorg on some Ubuntu versions. Xpra can use Xvfb instead of the Xorg based Xdummy for those cases. That's what our packages configure it to do. Do not run as root. > So I tried that, which instead gave this log: (snip) > 2018-06-05 23:59:00,998 Warning: zlib is the only compressor enabled > 2018-06-05 23:59:00,999 install and enable lzo or lz4 support for better > performance You have not installed the package or its dependencies correctly. > 2018-06-05 23:59:00,999 Warning: 'rencode' packet encoder not found > 2018-06-05 23:59:00,999 the other packet encoders are much slower Same. > 2018-06-05 23:59:00,999 server uuid is 26a9c4d0426b41c385acc3976739cdf8 > 2018-06-05 23:59:01,141 pulseaudio server started with pid 23259 > W: [pulseaudio] main.c: This program is not intended to be run as root > (unless --system is specified). > E: [autospawn] core-util.c: Home directory not accessible: Permission denied > W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. > E: [pulseaudio] main.c: Failed to acquire autospawn lock > 2018-06-05 23:59:01,150 using notification forwarder: > DBUSNotificationsForwarder(org.freedesktop.Notifications) > 2018-06-05 23:59:01,169 started child 'gnome-terminal' with pid 23282 > 2018-06-05 23:59:01,170 xpra server version 0.15.8 (r11211) Do not use this version. > 2018-06-05 23:59:01,170 running with pid 23242 > 2018-06-05 23:59:01,170 Warning: pulseaudio has terminated shortly after > startup. > 2018-06-05 23:59:01,170 Either fix the pulseaudio command line or use the > 'pulseaudio=no' option to avoid this warning. > 2018-06-05 23:59:01,170 usually, only a single pulseaudio instance can be > running for each user account, and one may be running already > 2018-06-05 23:59:01,260 you may want to disable mdns support to avoid this > 2018-06-05 23:59:01,264 xpra is ready. > Xlib: extension "GLX" missing on display ":100". > 2018-06-05 23:59:01,512 child 'gnome-terminal' with pid 23282 has terminated > > Connecting to this server ran as root using > $ xpra attach > gives the exact same output as before (and opens no gnome-terminal) > > Can somebody help me? Is the xpra version 0.15.8+dfsg-1 that I got from the > Linux Mint18.3/Ubuntu16.04 repository broken? Yes. > Or is xpra not usable on > current linux desktop systems in general? What do you suggest would be the > easiest way to get it functional, if thats possible on this system? Install the current version of xpra from xpra.org correctly. Cheers Antoine > > Thank you, > Kind regards, > Thomas K. > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From philip at tidepool.ca Sun Jun 17 20:15:30 2018 From: philip at tidepool.ca (Philip Loewen) Date: Sun, 17 Jun 2018 12:15:30 -0700 Subject: [winswitch] Strange read-only mounts on lubuntu 18.04 Message-ID: Here's a strange experience using xpra v2.3.1-r19531 as the server on a new installation of lubuntu 18.04. This is a fresh installation from the xpra.org repos. Here at my remote location, I can connect to the machine that serves Xpra using a direct ssh connection (not the Xpra client) and check my mounts. The results are unsurprising: $ mount | grep /dev/sd | sort /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro,stripe=32734,data=ordered) /dev/sda3 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/sda4 on /16.04 type ext4 (rw,noatime,data=ordered) But when I enter exactly the same command into a terminal window on the same machine but provided by an Xpra session, the results are quite different and surprising: $ mount | grep /dev/sd | sort /dev/sda1 on /home type ext4 (rw,noatime,errors=remount-ro,stripe=32734,data=ordered) /dev/sda1 on /root type ext4 (rw,noatime,errors=remount-ro,stripe=32734,data=ordered) /dev/sda1 on /tmp type ext4 (rw,noatime,errors=remount-ro,stripe=32734,data=ordered) /dev/sda1 on / type ext4 (ro,noatime,errors=remount-ro,stripe=32734,data=ordered) /dev/sda3 on /boot/efi type vfat (ro,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/sda4 on /16.04 type ext4 (ro,noatime,data=ordered) (The terminal application is lxterminal 0.3.1.) Note that all my usual mounts are read-only, not read-write, and there are strange new mount points not seen before. The read-only attribute interferes with the normal operation of many standard applications. The disk /dev/sda on the machine running the Xpra is healthy. I can repeat the direct inquiry via ssh shown first and get the same results any time *after* seeing the anomalous report coming through Xpra. I am mystified. Any proposed explanations and/or remedies for this situation (even me-too reports) would be most welcome. Thanks!??? - Philip From antoine at nagafix.co.uk Mon Jun 18 04:37:33 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 18 Jun 2018 10:37:33 +0700 Subject: [winswitch] Strange read-only mounts on lubuntu 18.04 In-Reply-To: References: Message-ID: <90d6c9fa-5a32-9c4e-c0ec-438f580392ff@nagafix.co.uk> (snip) > But when I enter exactly the same command into a terminal window on the > same machine but provided by an Xpra session, the results are quite > different and surprising: (snip) > Note that all my usual mounts are read-only, not read-write, and there > are strange new mount points not seen before. The read-only attribute > interferes with the normal operation of many standard applications. The > disk /dev/sda on the machine running the Xpra is healthy. I can repeat > the direct inquiry via ssh shown first and get the same results any time > *after* seeing the anomalous report coming through Xpra. > > I am mystified. Any proposed explanations and/or remedies for this > situation (even me-too reports) would be most welcome. Thanks!??? - Philip In order to better isolate individual sessions from the rest of the system, we use the system-wide proxy server to register them as proper systemd sessions. This includes setting "ProtectSystem" to "strict", for more details see: http://lists.devloop.org.uk/pipermail/shifter-users/2017-August/001990.html Cheers Antoine From anto.trande at gmail.com Sat Jun 23 11:14:20 2018 From: anto.trande at gmail.com (Antonio Trande) Date: Sat, 23 Jun 2018 12:14:20 +0200 Subject: [winswitch] Compiling error with Python 3.7.0-rc1 Message-ID: <6a10e86d-81e8-d2ec-e4d1-74895c46603c@fedoraproject.org> Hi all. On Fedora 29 (devel branch), we are already using Python-3.7.0-rc1 (and GCC-8.1.1). Recompiling xpra-2.3.1 i'm obtaining this error: gcc -pthread -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -D_GNU_SOURCE -fPIC -fwrapv -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -Ixpra/buffers -I/usr/include/python3.7m -c xpra/buffers/buffers.c -o build/temp.linux-x86_64-3.7/xpra/buffers/buffers.o -O3 -Wall -Werror -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection xpra/buffers/buffers.c: In function ?_object_as_buffer?: xpra/buffers/buffers.c:43:5: error: ?PyObject_AsReadBuffer? is deprecated [-Werror=deprecated-declarations] return PyObject_AsReadBuffer(obj, buffer, buffer_len); ^~~~~~ In file included from /usr/include/python3.7m/Python.h:128, from xpra/buffers/buffers.c:8: /usr/include/python3.7m/abstract.h:489:17: note: declared here PyAPI_FUNC(int) PyObject_AsReadBuffer(PyObject *obj, ^~~~~~~~~~~~~~~~~~~~~ xpra/buffers/buffers.c: In function ?_object_as_write_buffer?: xpra/buffers/buffers.c:56:5: error: ?PyObject_AsWriteBuffer? is deprecated [-Werror=deprecated-declarations] return PyObject_AsWriteBuffer(obj, buffer, buffer_len); ^~~~~~ In file included from /usr/include/python3.7m/Python.h:128, from xpra/buffers/buffers.c:8: /usr/include/python3.7m/abstract.h:500:17: note: declared here PyAPI_FUNC(int) PyObject_AsWriteBuffer(PyObject *obj, ^~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors error: command 'gcc' failed with exit status 1 Can you fix it please? Full build log: https://koji.fedoraproject.org/koji/getfile?taskID=27753977&volume=DEFAULT&name=build.log -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x5E212EE1D35568BE GPG key server: https://keys.fedoraproject.org/ From antoine at nagafix.co.uk Sat Jun 23 11:34:30 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 23 Jun 2018 17:34:30 +0700 Subject: [winswitch] Compiling error with Python 3.7.0-rc1 In-Reply-To: <6a10e86d-81e8-d2ec-e4d1-74895c46603c@fedoraproject.org> References: <6a10e86d-81e8-d2ec-e4d1-74895c46603c@fedoraproject.org> Message-ID: <069df259-c7f3-e109-7d68-ea30b410dd99@nagafix.co.uk> On 23/06/18 17:14, Antonio Trande via shifter-users wrote: > Hi all. > > On Fedora 29 (devel branch), we are already using Python-3.7.0-rc1 (and > GCC-8.1.1). Recompiling xpra-2.3.1 i'm obtaining this error: (snip) Please file a ticket. Until then you can compile with "--without-strict" and the warnings won't cause the build to fail. Thanks Antoine From antoine at nagafix.co.uk Tue Jun 26 21:30:16 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 27 Jun 2018 03:30:16 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.3.2 Message-ID: <8a79b16c-5a8d-37b0-f15e-b12e67e7486e@nagafix.co.uk> Hi, This update fixes a large number of issues, mostly cosmetic ones, none of them are really critical. There is no urgency to update. The buffer overflow sounds scary, but it only affects the GTK3 builds and those aren't the default on any platforms yet, it only triggers when OpenGL rendering is disabled and it is unlikely to be exploitable. The bandwidth-limit bypass can cause problems for those with budgeted bandwidth allocations on their servers. Release notes: * fix notification actions support with shadow servers * fix paint errors with reformatted images using outdated stride value * fix control commands that call window refresh * fix broken pipe error when the browser cancels downloading 'noicon' * fix spurious refresh events * fix missing bug report data due to path errors * fix XAUTHORITY environment variable getting clobbered * fix html5 window refresh not throttled when document is not invisible * fix non-opengl painting of windows with a padding area * fix rgb paint of mmap data with the python2 cairo backend * fix invalid clipboard toggle requests not ignored * fix missing context handler for keymap setup (crash possible) * fix proxy server test to use a signal to stop the test instance * fix invalid exception value in X11 atom bindings * fix bandwidth limit client bypass and connection errors * fix building CUDA kernels with GCC 8.1 * fix tray menu setup error when the clipboard is disabled * fix GTK3 buffer overflow with non-opengl backend * fix startup errors with pulseaudio if XDG_RUNTIME_DIR is missing * fix clipboard token send error when there are no targets * don't overwrite the dynamic system tray icon with default on startup * correctly disable desktop-scaling when mmap is enabled * skip repainting pointer overlay when the position is unchanged * prevent authenticated users from shutting down proxy servers * don't turn off notifications when we don't have a forwarder instance * don't try to log an exception that does not exist * allow the user to disable all video encoders and csc modules * send missing exception details to server with remote-logging * avoid RFB errors if screen capture fails * avoid further errors when shadow capture fails * recommend the dbus-x11 with the DEB package The source: https://xpra.org/src/ Downloads: https://xpra.org/trac/wiki/Download Cheers Antoine