xpra icon
Bug tracker and wiki

Opened 7 months ago

Closed 7 months ago

Last modified 6 months ago

#2260 closed defect (worksforme)

client failed to specify any supported encodings

Reported by: weberjn Owned by: weberjn
Priority: major Milestone: 3.0
Component: android Version: 2.5.x
Keywords: Cc:

Description (last modified by Antoine Martin)

Xpra windows revision r22235 cannot connect any longer to server.

server log:

2019-04-05 09:41:43,609 Error setting up new connection for
2019-04-05 09:41:43,609  Protocol(unix-domain socket:/run/user/1000/xpra/fedo-100):
2019-04-05 09:41:43,610  client failed to specify any supported encodings
[weberjn@fedo ~]$ xpra version
2.5-r22144
[weberjn@fedo ~]$ uname -a
Linux fedo 5.0.5-200.fc29.armv7hl #1 SMP Wed Mar 27 22:48:16 UTC 2019 armv7l armv7l armv7l GNU/Linux

Change History (10)

comment:1 Changed 7 months ago by Antoine Martin

Description: modified (diff)
Owner: changed from Antoine Martin to weberjn

Arm is not a supported platform, so without more information on how you built this version, it is impossible to help you.
See wiki/ReportingBugs.

comment:2 Changed 7 months ago by weberjn

I did not build, I followed "the ​repository installation instructions for winswitch" on https://xpra.org/trac/wiki/Download#Linux

In the mean time I went back to 2.4.3 on Windows, same error.

comment:3 Changed 7 months ago by Antoine Martin

I did not build, I followed "the ​repository installation instructions for winswitch"
Linux fedo 5.0.5-200.fc29.armv7hl #1 SMP Wed Mar 27 22:48:16 UTC 2019 armv7l armv7l armv7l GNU/Linux

We do not provide packages for arm. You must have got those from somewhere else.

comment:4 Changed 7 months ago by weberjn

$ yum info xpra
Fedora Modular 29 - armhfp                                                                             757 kB/s | 1.4 MB     00:01
Fedora Modular 29 - armhfp - Updates                                                                   589 kB/s | 2.0 MB     00:03
Fedora 29 - armhfp - Updates                                                                           1.1 MB/s |  22 MB     00:19
Fedora 29 - armhfp                                                                                     1.1 MB/s |  56 MB     00:49
Winswitch 29 - armhfp                                                                                   12 kB/s | 3.5 kB     00:00
Failed to synchronize cache for repo 'winswitch'
Ignoring repositories: winswitch
Last metadata expiration check: 0:00:03 ago on Tue 09 Apr 2019 11:17:48 PM CEST.
Installed Packages
Name         : xpra
Version      : 2.5.0
Release      : 1.fc29
Architecture : armv7hl
Size         : 16 M
Source       : xpra-2.5.0-1.fc29.src.rpm
Repository   : @System
From repo    : updates
Summary      : Remote display server for applications and desktops
URL          : https://www.xpra.org/
...

comment:5 Changed 7 months ago by Antoine Martin

From repo : updates

So this is not from xpra's repo but from fedora's.
They must have packaged something wrong.
I'm pretty sure that the same client would work just fine if you were connecting to an x86 system running xpra's packages.

As per comment:1, please provide more details, like the server log with --debug all.
Please also include:

  • the output of python /usr/lib*/python2.7/site-packages/xpra/codecs/loader.py
  • the output of python /usr/lib*/python2.7/site-packages/xpra/net/net_util.py

You may also want to apply r22369 to see the values for the encoding options before the server decides to bail out.

comment:6 Changed 7 months ago by Antoine Martin

Resolution: worksforme
Status: newclosed

Not heard back.

comment:7 Changed 6 months ago by weberjn

Gave up on the Windows client. Now running VirtualBox?+Devuan+Xpra client against the Fedora/Arm? server. Works great.

comment:8 Changed 6 months ago by Antoine Martin

Gave up on the Windows client.

There windows client is very well tested. I very much doubt that this is the problem.

The only time I have ever seen this error is when going through a proxy server and the final destination server requires authentication, which is not supplied by the proxy server.
But since you never provided the full details as per comment:1 (ie: command lines, etc), we will probably never know.

comment:9 Changed 6 months ago by weberjn

[weberjn@fedo ~]$ yum info xpra
...
Installed Packages
Name : xpra
Version : 2.5.0
Release : 1.fc30
Architecture : armv7hl
Size : 17 M
Source : xpra-2.5.0-1.fc30.src.rpm
Repository : @System
From repo : fedora

The client was the windows exe, so no command line. And, as the virtualboxed Linux Client is working from the same Windows machine, this should be no server or firewall problem.

comment:10 Changed 6 months ago by Antoine Martin

The client was the windows exe, so no command line.

The windows installer includes command line tools just like the other platforms (run xpra_cmd.exe). Those should be used to get reliable debug output.

My original guess remains: the package you are using is borked, maybe the linux client deals with it more gracefully.

Note: See TracTickets for help on using tickets.