On 14/05/2020 13:08, Luca Manganelli via shifter-users wrote: > Hello, > > I have two systems: > > 1) at work with Fedora 32 > 2) at home with Ubuntu 18.04 > > both do have Xpra 4.0. > > In Xpra 3.0 I had always executed this command successfully: > > xpra start ssh://SSH_HOST --start-child=pidgin (or whatever any application) > > but in 4.0 this throws this error: > > 2020-05-14 07:47:27,269 Authentication (password) successful! > 2020-05-14 07:47:28,036 keyboard settings: rules=evdev, model=pc105, > layout=it > 2020-05-14 07:47:28,130 desktop size is 1920x1080 with 1 screen: > 2020-05-14 07:47:28,130 :0.0 (508x285 mm - DPI: 96x96) workarea: 1920x1044 > 2020-05-14 07:47:28,130 DP-3 (520x320 mm - DPI: 93x85) > 2020-05-14 07:47:57,860 connection timed out > > the remote logs don't tell anything particular Thanks for reporting this bug. Yet again, one of the very last features to go in (MS Windows proxy support) has caused a regression elsewhere.. Sorry about that. We'll try to do better in the future.
The fix is trivial: http://xpra.org/trac/changeset/26351 So you can just apply it by hand to your installation, wait for the 4.0.1 release, or start your sessions in two steps: xpra start ssh://SSH_HOST --start=whatever --attach=no xpra attach ssh://SSH_HOST Cheers, Antoine _______________________________________________ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
