X-forwarding no longer works
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection.
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /home/nanook/
debug1: Server accepts key: /home/nanook/
debug1: Authentication succeeded (publickey).
Authenticated to igloo.eskimo.com ([204.122.
debug1: channel 0: new [client-session]
debug1: Requesting <email address hidden>
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_
debug1: Remote: /home/nanook/
debug1: Remote: /home/nanook/
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_
debug1: client_
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 2 clearing O_NONBLOCK
Connection to igloo.eskimo.com closed.
Transferred: sent 3748, received 3820 bytes, in 6.4 seconds
Bytes per second: sent 589.4, received 600.8
I don't see anything obviously wrong here but still it does not work, I get:
xclock
Error: Can't open display:
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ssh (not installed)
Uname: Linux 5.13.19 x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: MATE
Date: Tue Nov 2 17:31:14 2021
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)
Hello Robert and thanks for your bug report. You wrote:
> I recently upgraded my debian shell server to Bullet
but I'm not sure I get what you mean. Is it a Debian system or an Ubuntu system? If it's upgrading a Debian system that broke your setup then there's nothing I can see that points to a bug in Ubuntu. Moreover: what is Bullet? Did you mean Bullseye or Bookworm?
If you think there's actually a bug in Ubuntu here please share more of your reasoning, possibly providing a reproducer, e.g. by ssh -X to a container or VM. I'm marking this bug report as Incomplete for the moment. Feel free to change it back to New after commenting back. Thanks!