Bug 239395

Created attachment 154313 [details]
RPMs installed on box_b

Does 'sudo /usr/sbin/virt-manager' work?

Are both box_b and box_c fully updated from Fedora updates?

usermode probably doesn't forward/set $XAUTHORITY right.

> Does 'sudo /usr/sbin/virt-manager' work?

Yes!

> Are both box_b and box_c fully updated from Fedora updates?

Yes, at least most of the packages I thought would make any difference.

Created attachment 154377 [details]
RPMs installed on box_c

> Are both box_b and box_c fully updated from Fedora updates?

Here's a more accurate answer: No.

But I'm happy to try updating all or some of the packages on one or both machines.

Also see similar bug 239570.  It's odd that I can reproduce the common symptoms
on every environment I have EXCEPT the Fedora 6 one noted in this bug (239395).

Please run the following commands:
  uname -n
  cat /etc/hosts
  echo $DISPLAY
  echo $XAUTHORITY
  xauth list
  su - -c '(echo $XAUTHORITY; xauth list)'

on both box_b and box_c, and paste the results.

Created attachment 154793 [details]
requested info on box_b and box_c

Here is the information you requested.

Thank you, reproduced.

This is unrelated to usermode: (sudo su - -c xeyes) doesn't work either.

This happens because ssh uses the default Xauthority file, and does not set
XAUTHORITY, so libXau uses $HOME/.Xauthority.  sudo changes the uid, but not
$HOME, so the original $HOME/.Xauthority is still used.  Then, userhelper (or su
-) use the pam_xauth module.

pam_xauth does not use $HOME/.Xauthority, but "invoking user's home
directory"/.Xauthority, i.e. /root/.Xauthority, which does not exist.

So, pam_xauth should be using $HOME/.Xauthority if XAUTHORITY is not set and
$HOME/.Xauthority is readable by the invoking user.

You can use (XAUTHORITY=~/.Xauthority sudo virt-manager) as a work-around.

I'm afraid the above still does not explain the difference in behavior between
box_b and box_c.

This would be only a workaround. What's IMHO really broken is environment as set
up by sudo. It should call pam_xauth as well but currently simply adding the
module to sudo pam configuration doesn't help because it is calling
pam_open_session with empty $DISPLAY.

I'm not sure whether the behavior of sudo is incorrect, but the behavior of
pam_xauth (using a different default path for .Xauthority than the X libraries_)
is definitely incorrect.

Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

bumping this issue for fedora 10. From fedora 10 box to fedora 10 box using ssh -X or ssh -Y. env shows DISPLAY as localhost:10.0 and attempting to run any app (gnome-terminal, evolution..etc), errors with "Cannot open display:". From Fedora 10 box to Fedora 8 box using ssh -[XY] everything works. In Fedora 8, env shows localhost:10.0.

/etc/ssh ssh_config and sshd_config same between both fedora 10 and fedora 8 hosts.

Attempting to use straight ssh session, xhost + and export DISPLAY= does nothing and gives the same errors.

Gregory, are you talking about running apps through sudo or directly? Because this bug is only about problems when X apps are run from ssh session through sudo. If this is about directly running the X apps from ssh session it would be a completely new problem, so please open a new bug report for it against openssh.

Hi,

I'm now noticing this problem on Fedora 10 x86_64 too. I used to be able to successefully run 

 sudo virt-manager

on a Centos 5 box with X forwarding activated and the virt-manager gui would display locally.

I haven't done it in a while and both operating systems have had packages updated several times since I last successfully ran it, so I'm not sure when the change occurred which is causing the problem. Other that package updates, nothing that I can think of on either the ssh server or client has been modified.

N.B. I'm running sshd on a non-standard port.

Here's an example of the ssh session:

[lnik@fedora10 ~]$ ssh -X -p 3923 centos5.example.com
lnik.com's password: 
Last login: Sun Apr 26 01:06:21 2009 from example123.dyn.example.com
###########################################################################
# Centos5
#
###########################################################################
/usr/bin/xauth:  creating new authority file /home/lnik/.Xauthority
[lnik@centos5 ~]$ sudo virt-manager 
X11 connection rejected because of wrong authentication.
The application 'virt-manager.py' lost its connection to the display localhost:10.0;
most likely the X server was shut down or you killed/destroyed
the application.
[lnik@centos5 ~]$

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.