-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian test failure: asyncssh.misc.ChannelOpenError: Channel Open Error: X11 forwarding request failed #81
Comments
Would it be possible to try this again with AsyncSSH 1.9.0? I checked in the fix a4aa89a a month or so ago that seems like it might address these failures. This was after 1.8.1 was released, though. |
thanks @ronf for the quick reply! sadly due to the late development phase Debian is at the moment, it is not possible to upgrade to a new release. Do you think that commit is all that needs to be applied to make those failures go again? we could take that and apply it to the 1.8.1 version we have in our archive |
The fix above was actually a correction to the fix 51545e0, and you'd probably need both changes if you wanted to cherry-pick this. I don't really know for sure if this will fix the Debian problem, as I haven't seen any failures of this sort in my Linux unit testing on Ubuntu. Unfortunately, there tracebacks don't point at a specific problem, and just indicate the server-side of the X11 forwarding failed for some reason. If someone can provide me remote access to a VM having this problem, I'd be happy to take a closer look. |
Closing this for now - feel free to open a new issue if the problem reappears. |
Sorry for the very late answer. We already had those patches in Debian. I'll update to the latest version and see if it goes away. I didn't have the failures either in my environment. |
Hello,
in Debian we got this report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854701:
version of asyncssh is 1.8.1
could you have a look at what's causing this and how we can address it? currently this problem is creating a bug severe enough that asyncssh may risk to be excluded from the upcoming debian release (aka stretch)
thanks!
The text was updated successfully, but these errors were encountered: