kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Brendan Powers, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Tags added: hardy needs-kernel-logs needs-upstream-testing
regression-release

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/269954

Title:
  ssh -X breaks Xauthority on NFS mounted home dir

Status in “linux” package in Ubuntu:
  Incomplete
Status in Debian GNU/Linux:
  Confirmed

Bug description:
  When using an nfs mounted home directory, using ssh to connect and run
  a X11 app from the nfs server causes X applications to break.

  Steps to reproduct the problem
  1) have to computers(A and B) with ubuntu 8.04 installed
  2) Export /home from computer A, and mount it on computer B
  3) Create a user that has the same username, home directory, and UID on both computers
  4) Log into computer B with the user that was just created, and ssh into box A and run an X application (ssh -X boxa xterm)
  5) In another terminal, try to run another X app on box b as the same user.

  What is supposed to happen: The X app on box B runs properly
  What actually happens: The X app will fail with an error like "Xlib: connection to ":0.0" refused by server" about 50% of the time

  This can be fixed by running "cat ~/.Xauthority".
  Also sometimes running "ls -al ~/.Xauthority" will result in a "stale nfs file handle" error.

  I assume this is because the Xauthority file is removed, and then a
  new one is created when ssh sets up credentials on computer A. This
  causes the file inode number to change, causing the stale file handle
  errors on computer B. However, this problem did not occur in ubuntu
  feisty. I havn't tried it with gutsy. I've tried installing the
  packages for xauth and libxau6 from feisty, but it did not fix the
  problem. So I'm guessing its an ssh issue, but i could be wrong.

  Someone reported the same issue on the ubuntu mailing list, but didn't seem to file a bug report that i could find.
  https://lists.ubuntu.com/archives/ubuntu-users/2008-July/152242.html

  I'm using ubuntu 8.04.1, also had the same problem with 8.04.0. It worked fine in ubuntu 7.04.
  Package Versions
  ==========
  openssh-client: 1:4.7p1-8ubuntu1.2
  openssh-server: 1:4.7p1-8ubuntu1.2
  xauth: 1:1.0.2-2
  libxau6: 1:1.0.3-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269954/+subscriptions