*** This bug is a duplicate of bug 882878 ***
https://bugs.launchpad.net/bugs/882878
** This bug has been marked a duplicate of bug 882878
With IPv6 disabled, openssh will not forward X connections
--
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a duplicate of bug 882878 ***
https://bugs.launchpad.net/bugs/882878
** This bug has been marked a duplicate of bug 882878
With IPv6 disabled, openssh will not forward X connections
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also see this bug when using 10.04.4.
The fix for me was adding AddressFamily inet to the sshd_config file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/434799
Title:
X11
I also see this bug when using 10.04.4.
The fix for me was adding AddressFamily inet to the sshd_config file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/434799
Title:
X11 forwarding via SSH
My case:
# Go to workstation
r...@laptop:~$ ssh -X workstation
# Check for $DISPLAY
r...@workstation:~$ env | grep DISPLAY || echo No display found
No display found
# Check log
workstation:~$ sudo -s
workstation:~# grep X11 /var/log/auth.log
Sep 23 16:33:10 workstation sshd[14105]: error:
My case:
# Go to workstation
r...@laptop:~$ ssh -X workstation
# Check for $DISPLAY
r...@workstation:~$ env | grep DISPLAY || echo No display found
No display found
# Check log
workstation:~$ sudo -s
workstation:~# grep X11 /var/log/auth.log
Sep 23 16:33:10 workstation sshd[14105]: error:
This bug affected me on Lucid as well.
$ apt-show-versions |grep ssh
openssh-client/lucid-updates uptodate 1:5.3p1-3ubuntu4
openssh-server/lucid-updates uptodate 1:5.3p1-3ubuntu4
ssh-askpass-gnome/lucid-updates uptodate 1:5.3p1-3ubuntu4
$ grep X11 /etc/ssh/sshd_config
X11Forwarding yes
p.s.
I was able to connect to other servers and tunnel X11 to them, at the same time
as I was experiencing this issue with lucid.
$ grep -i family /etc/ssh/sshd_config
$
$ grep 127 /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
$ ifconfig lo
loLink encap:Local Loopback
This bug affected me on Lucid as well.
$ apt-show-versions |grep ssh
openssh-client/lucid-updates uptodate 1:5.3p1-3ubuntu4
openssh-server/lucid-updates uptodate 1:5.3p1-3ubuntu4
ssh-askpass-gnome/lucid-updates uptodate 1:5.3p1-3ubuntu4
$ grep X11 /etc/ssh/sshd_config
X11Forwarding yes
p.s.
I was able to connect to other servers and tunnel X11 to them, at the same time
as I was experiencing this issue with lucid.
$ grep -i family /etc/ssh/sshd_config
$
$ grep 127 /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
$ ifconfig lo
loLink encap:Local Loopback
Same for me on 10.04
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Dear All,
This bug affects me from lucid.
As I don't have ipv6 available, I am used to de-activate it. But this bug still
affected me.
I tried the workarounds.
AddressFamily inet to sshd_config works for me.
add the -4 to the exec line in /etc/init/ssh.conf .. works for me
also it
Dear All,
This bug affects me from lucid.
As I don't have ipv6 available, I am used to de-activate it. But this bug still
affected me.
I tried the workarounds.
AddressFamily inet to sshd_config works for me.
add the -4 to the exec line in /etc/init/ssh.conf .. works for me
also it
bump?
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
HAHA! (small dance around)
I found it! Nothing messes modern linux up worse than not having the
loopback interface configured properly, to 127.0.0.1, also in
/etc/hosts.
This is the source of the ODDEST bugs!
--
X11 forwarding via SSH does not work after upgrade to karmic
bump?
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
HAHA! (small dance around)
I found it! Nothing messes modern linux up worse than not having the
loopback interface configured properly, to 127.0.0.1, also in
/etc/hosts.
This is the source of the ODDEST bugs!
--
X11 forwarding via SSH does not work after upgrade to karmic
Mine is not yet solved, on Lucid. ALso, will you please decide if you want or
not the line
AddressFamily inet ??
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server
Mine is not yet solved, on Lucid. ALso, will you please decide if you want or
not the line
AddressFamily inet ??
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks guys .. this solved mine as well
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs
Thanks guys .. this solved mine as well
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Andrew, in my experience the problem is that restarting a service (i.e.
service ssh restart) does not apply configuration changes.
So please try like this:
initctl reload-configuration
sevice ssh stop
service ssh start
It worked for me (while restart did not work).
--
X11 forwarding via SSH
yota, you're correct. stop + start restart. So #20 does also work
for me now. Thanks, Andrew.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Andrew, in my experience the problem is that restarting a service (i.e.
service ssh restart) does not apply configuration changes.
So please try like this:
initctl reload-configuration
sevice ssh stop
service ssh start
It worked for me (while restart did not work).
--
X11 forwarding via SSH
yota, you're correct. stop + start restart. So #20 does also work
for me now. Thanks, Andrew.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can anyone else confirm that #20 does not work for them? That is, if
you do the following:
* remove AddressFamily inet from sshd_config
* add -4 after exec /usr/sbin/sshd in /etc/init/ssh/conf
* run
initctl reload-configuration
restart sshd
then do you still have this problem? Does
pgrep
Can anyone else confirm that #20 does not work for them? That is, if
you do the following:
* remove AddressFamily inet from sshd_config
* add -4 after exec /usr/sbin/sshd in /etc/init/ssh/conf
* run
initctl reload-configuration
restart sshd
then do you still have this problem? Does
pgrep
Same thing as #24 happened in my case.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs
Same thing as #24 happened in my case.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I upgraded to Lucid last weekend and now X Forwarding is not working
again:
$ echo $DISPLAY
$ cat /etc/default/ssh |grep OPTS
SSHD_OPTS=-4
$ cat /etc/ssh/sshd_config |grep Forward
X11Forwarding yes
Any ideas?
--
X11 forwarding via SSH does not work after upgrade to karmic
Also, same error message on /var/log/auth.log:
May 3 15:59:36 ubuntu sshd[1331]: error: Failed to allocate internet-
domain X11 display socket.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you
In Lucid the upstart script /etc/init/ssh.conf does not source
/etc/default/ssh, and it seems to be ignoring it on purpose looking at
the comment:
# if you used to set SSHD_OPTS in /etc/default/ssh, you can change the
# 'exec' line here instead
the quickfix is to add the -4 to the exec line in
Confirmed that this is broken again in Lucid, and I agree with yota:
the purpose of /etc/default/* is to provide supported ways for
administrators to modify services' behavior without having to modify
their startup scripts. It's a regression to stop supporting
/etc/default/ssh.
--
X11
Setting
AddressFamily inet
in /etc/ssh/sshd_config and restarting sshd does work around this
problem.
** Description changed:
I had a proper configuration on jaunty (sshd_config) so I could ssh into
that machine and run X11 applications there with X11 forwarding, so I
could use apps
I can confirm adding AddressFamily inet to sshd_config fixed the
problem for me after a SSH restart:
$ echo $DISPLAY
localhost:10.0
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member
In Lucid the upstart script /etc/init/ssh.conf does not source
/etc/default/ssh, and it seems to be ignoring it on purpose looking at
the comment:
# if you used to set SSHD_OPTS in /etc/default/ssh, you can change the
# 'exec' line here instead
the quickfix is to add the -4 to the exec line in
Confirmed that this is broken again in Lucid, and I agree with yota:
the purpose of /etc/default/* is to provide supported ways for
administrators to modify services' behavior without having to modify
their startup scripts. It's a regression to stop supporting
/etc/default/ssh.
--
X11
Also, the revised workaround in #20 does not work for me. I edited
/etc/init/ssh.conf as suggested, then ran
initctl reload-configuration
restart ssh
but for some reason the -4 parameter isn't taking effect. ps shows sshd
running as just /usr/sbin/sshd with no argument, netstat shows sshd
Setting
AddressFamily inet
in /etc/ssh/sshd_config and restarting sshd does work around this
problem.
** Description changed:
I had a proper configuration on jaunty (sshd_config) so I could ssh into
that machine and run X11 applications there with X11 forwarding, so I
could use apps
I can confirm adding AddressFamily inet to sshd_config fixed the
problem for me after a SSH restart:
$ echo $DISPLAY
localhost:10.0
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member
I upgraded to Lucid last weekend and now X Forwarding is not working
again:
$ echo $DISPLAY
$ cat /etc/default/ssh |grep OPTS
SSHD_OPTS=-4
$ cat /etc/ssh/sshd_config |grep Forward
X11Forwarding yes
Any ideas?
--
X11 forwarding via SSH does not work after upgrade to karmic
Also, same error message on /var/log/auth.log:
May 3 15:59:36 ubuntu sshd[1331]: error: Failed to allocate internet-
domain X11 display socket.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you
** Tags added: ipv6
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
** Tags added: ipv6
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm this bug. It's on both Karmic and Lucid, no matter which
client I use.
See attachments for sshd-debug info on both working and not-working
situations, as well as the ssh version info.
** Attachment added: sshd_inet6_not_working
** Attachment added: sshd_inet_working
http://launchpadlibrarian.net/40162148/sshd_inet_working
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: sshd_version
http://launchpadlibrarian.net/40162174/sshd_version
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I can confirm this bug. It's on both Karmic and Lucid, no matter which
client I use.
See attachments for sshd-debug info on both working and not-working
situations, as well as the ssh version info.
** Attachment added: sshd_inet6_not_working
** Attachment added: sshd_inet_working
http://launchpadlibrarian.net/40162148/sshd_inet_working
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: sshd_version
http://launchpadlibrarian.net/40162174/sshd_version
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm this ... but this error appeared in the system where IPv6
was disabled in the kernel. In a fresh installation, this error does not
occur.
** Changed in: openssh (Ubuntu)
Status: Incomplete = Confirmed
--
X11 forwarding via SSH does not work after upgrade to karmic
I can confirm this ... but this error appeared in the system where IPv6
was disabled in the kernel. In a fresh installation, this error does not
occur.
** Changed in: openssh (Ubuntu)
Status: Incomplete = Confirmed
--
X11 forwarding via SSH does not work after upgrade to karmic
Same problem here, same entries in auth.log - but I did a clean install
of Karmic, this is NOT an upgrade from 9.04.
I can confirm, that workaround from asaijo works (thank you).
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received
asaijo's fix worked great.
This is not the first IPv4-related tweak I've had to perform since
upgrading to Karmic. I had to disable IPv6 on my system because DNS
queries took 15-30 seconds... and now this.
This fix should be kept available for those who upgraded! Thanks
asaijo!!
--
X11
Same problem here, same entries in auth.log - but I did a clean install
of Karmic, this is NOT an upgrade from 9.04.
I can confirm, that workaround from asaijo works (thank you).
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received
asaijo's fix worked great.
This is not the first IPv4-related tweak I've had to perform since
upgrading to Karmic. I had to disable IPv6 on my system because DNS
queries took 15-30 seconds... and now this.
This fix should be kept available for those who upgraded! Thanks
asaijo!!
--
X11
I can fix this problem.
Change /etc/default/ssh/ssh:
SSHD_OPTS=
to
SSHD_OPTS=-4
This lets the ssh-server use onlyq IPv4.
After chaning this setting, you should restart ssh-server:
# /etc/init.d/ssh restart
--
X11 forwarding via SSH does not work after upgrade to karmic
It worked!! Many thanks!
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
I can fix this problem.
Change /etc/default/ssh/ssh:
SSHD_OPTS=
to
SSHD_OPTS=-4
This lets the ssh-server use onlyq IPv4.
After chaning this setting, you should restart ssh-server:
# /etc/init.d/ssh restart
--
X11 forwarding via SSH does not work after upgrade to karmic
It worked!! Many thanks!
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, I'm using Putty from a Windows box and the same happens on the Terminal
app on Mac OS X.
The version of Putty I'm using is 0.60. In regards to SSH on my Karmic box:
$ dpkg -l |grep openssh
ii openssh-client 1:5.1p1-6ubuntu2
Yes, I'm using Putty from a Windows box and the same happens on the Terminal
app on Mac OS X.
The version of Putty I'm using is 0.60. In regards to SSH on my Karmic box:
$ dpkg -l |grep openssh
ii openssh-client 1:5.1p1-6ubuntu2
Is everybody using PuTTY as an ssh client? If not it would be quite
helpful to know what ssh client and package version with which you are
experiencing this bug.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug
Is everybody using PuTTY as an ssh client? If not it would be quite
helpful to know what ssh client and package version with which you are
experiencing this bug.
--
X11 forwarding via SSH does not work after upgrade to karmic
https://bugs.launchpad.net/bugs/434799
You received this bug
I also have this problem. For me it reports the following:
pa...@palsa-eeepc:~$ xeyes
X11 connection rejected because of wrong authentication.
Error: Can't open display: palsa-eeepc:10.0
pa...@palsa-eeepc:~$
--
X11 forwarding via SSH does not work after upgrade to karmic
I also have this problem. For me it reports the following:
pa...@palsa-eeepc:~$ xeyes
X11 connection rejected because of wrong authentication.
Error: Can't open display: palsa-eeepc:10.0
pa...@palsa-eeepc:~$
--
X11 forwarding via SSH does not work after upgrade to karmic
I'm having the exact same problem after upgrading to Karmic. I've used
Ubuntu since Feisty and this is the first time I ever experienced
problems with X forwarding on SSH. It worked fine on Jaunty. Basically
I'm experiencing the same issues as reported:
$ env | grep DISPLAY
$ echo $DISPLAY
$
Forgot to mention the loopback address is properly configured on my box:
$ ifconfig lo
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:139234 errors:0 dropped:0 overruns:0 frame:0
I'm having the exact same problem after upgrading to Karmic. I've used
Ubuntu since Feisty and this is the first time I ever experienced
problems with X forwarding on SSH. It worked fine on Jaunty. Basically
I'm experiencing the same issues as reported:
$ env | grep DISPLAY
$ echo $DISPLAY
$
Forgot to mention the loopback address is properly configured on my box:
$ ifconfig lo
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:139234 errors:0 dropped:0 overruns:0 frame:0
I see the same problem, in a repeatable way. I upgraded from 9.04 to
9.10. The ssh server was configured to allow X11 forwarding:
$ cat /etc/ssh/sshd_config | grep X11
X11Forwarding yes
X11UseLocalhost yes
X11DisplayOffset 10
When I connect from another machine using the PuTTY ssh client, I can
** Changed in: openssh (Ubuntu)
Status: Invalid = Confirmed
** Changed in: openssh (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: openssh (Ubuntu)
Status: Incomplete = New
** Changed in: openssh (Ubuntu)
Status: New = Incomplete
--
X11 forwarding via SSH
I've been unable to recreate this bug when ssh'ing from an Jaunty system
using openssh-client version 1:5.1p1-5ubutu1 to a Karmic system with
openssh-server version 1:5.1p1-6ubuntu1. Could you please set the
LogLevel to DEBUG on the server and include '/var/log/auth.log' with the
failure?
I unable to reproduce it either, but it was reproducable then. So I
suppose this bug is already fixed and/or there was some problem with my
config. I set the status to invalid then, if it's OK. Thanks!
** Changed in: openssh (Ubuntu)
Status: Incomplete = Invalid
--
X11 forwarding via SSH
I've been unable to recreate this bug when ssh'ing from an Jaunty system
using openssh-client version 1:5.1p1-5ubutu1 to a Karmic system with
openssh-server version 1:5.1p1-6ubuntu1. Could you please set the
LogLevel to DEBUG on the server and include '/var/log/auth.log' with the
failure?
I unable to reproduce it either, but it was reproducable then. So I
suppose this bug is already fixed and/or there was some problem with my
config. I set the status to invalid then, if it's OK. Thanks!
** Changed in: openssh (Ubuntu)
Status: Incomplete = Invalid
--
X11 forwarding via SSH
Also I am not sure if it's related but if I do X forwarding via SSH
_from_ that karmic box, it works, but I got this message too:
Warning: No xauth data; using fake authentication data for X11
forwarding.
But sine it works anyway it does not matter too much for me, the problem
is about starting
Also I am not sure if it's related but if I do X forwarding via SSH
_from_ that karmic box, it works, but I got this message too:
Warning: No xauth data; using fake authentication data for X11
forwarding.
But sine it works anyway it does not matter too much for me, the problem
is about starting
78 matches
Mail list logo
