Bug#357371: marked as done (ssh: fails to find xauth)
Your message dated Sat, 15 Apr 2006 10:40:52 -0400
with message-id <20060415144051.GA7111@andromeda>
and subject line Bug#354127: Acknowledgement (ssh: X forwarding stopped working, no changes to config files)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: ssh: fails to find xauth
- From: Andrei Lahun <zhirnyi@yahoo.com>
- Date: Thu, 16 Mar 2006 22:59:01 +0100
- Message-id: <20060316220145.5543673193@smtp2-g19.free.fr>
Package: ssh
Version: 1:4.2p1-7
Severity: normal
After installing new xbase-clients built from xorg 7.0
X11 forwarding stopped to work. New package xbase-clients
install xauth in /usr/bin ,but ssh expect it in /usr/bin/X11
and because it cannot find X11 forwarding is not possible.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.15
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) (ignored: LC_ALL set to ru_RU.KOI8-R)
Versions of packages ssh depends on:
ii openssh-client 1:4.2p1-7 Secure shell client, an rlogin/rsh
ii openssh-server 1:4.2p1-7 Secure shell server, an rshd repla
-- debconf information excluded
--- End Message ---
--- Begin Message ---
(Unversioned close since this isn't strictly an sssh problem, I think)
On Sat, Apr 15, 2006 at 01:17:25PM +0800, Clayton wrote:
> This problem seems to have gone away in the last couple of days (I
> am not sure what software update did the trick) so this bug report
> could be closed.
Right, I'm not sure either, but it WFM too :)
--- End Message ---
Reply to: