I don't understand why this bug is marked as incomplete. I've posted
everything I've been asked for.
I can't reproduce the bug even using the configuration files posted.
The bug states that it occurs upgrading from gutsy to hardy, did you tried that?
--
ssh -X no longer works
it even happens in localhost:
ssh -X 127.0.0.1
Last login: Wed Mar 19 23:49:11 2008
[EMAIL PROTECTED]:~$ firefox
Error: cannot open display: localhost:10.0
--
ssh -X no longer works
https://bugs.launchpad.net/bugs/202508
You received this bug notification because you are a member of Ubuntu
I can't believe it was as simple as adding localhost in my /etc/hosts
file...
cat /etc/hosts
192.168.1.2 cube
127.0.0.1 macbook localhost
#127.0.1.1 macbook
#127.0.0.1 hogar
# The following lines are desirable for IPv6 capable hosts
#::1 ip6-localhost ip6-loopback
#fe00::0 ip6-localnet
#ff00::0
Any updates? The bug is mark as incomplete but I've included all
information needed, or at least what was mentioned.
--
ssh -X no longer works
https://bugs.launchpad.net/bugs/202508
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh
** Changed in: openssh (Ubuntu)
Status: Incomplete = New
--
ssh -X no longer works
https://bugs.launchpad.net/bugs/202508
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
On Sat, Apr 5, 2008 at 4:13 AM, kmon [EMAIL PROTECTED] wrote:
I don't understand why sshd complains about:
Bind to port 2 on 0.0.0.0 failed: Address already in use. (in the sshd
output)
See Bug #129789. This error can be due to ssh binding to the same
port on both ipv6 and ipv4.
If
sshd -p 2 -ddd output
** Attachment added: sshd -p 2 -ddd
http://launchpadlibrarian.net/13129958/sshd%20-p%202%20-ddd
--
ssh -X no longer works
https://bugs.launchpad.net/bugs/202508
You received this bug notification because you are a member of Ubuntu
Server Team, which is
On the server machine:
netstat -a -n --program | grep 2
shows nothing, so the port doesn't seem to be in use before launching
sshd.
I don't understand why sshd complains about:
Bind to port 2 on 0.0.0.0 failed: Address already in use. (in the sshd
output)
Thanks
--
ssh -X no longer
Keith: ssh doesn't display progress bars; chances are this is a problem
at a higher layer.
kmon: Firstly, could you please try upgrading the server to at least
1:4.7p1-5ubuntu1 and see if that fixes your problem? It's possible that
something was bound to just the IPv6 version of :10.0.
If that
