Description of problem: ssh client doesn't find xauth as it looks for it in /usr/openwin/bin/xauth while xauth is in /usr/bin/xauth. I get the following warning for example when running mgarepo co <some_pkgname>: Warning: No xauth data; using fake authentication data for X11 forwarding. Version-Release number of selected component (if applicable): openssh-clients-5.6p1-4.mga1 How reproducible: run: mgarepo co <some_pkgname> Solution: the solution from the Gentoo Wiki also applies to Mageia, I tested it on my Mageia alpha install and I no longer get the warning. Add: XAuthLocation /usr/bin/xauth to /etc/ssh/ssh_config below the 'Host *' line. This should really be added by default in the Mageia ssh client package. Reproducible: Steps to Reproduce:
Please post your ~/.ssh/config (remove any private/sensitive data).
Keywords: (none) => NEEDINFO
It's the one specified here: http://mageia.org/wiki/doku.php?id=basic_ssh_configuration_for_packagers#editing_ssh_config_and_ssh_agent_forwarding -------- Host svn.mageia.org pkgsubmit.mageia.org ForwardAgent yes User tux99 --------
This is weird, today I can't reproduce this issue anymore. If I comment out "XAuthLocation /usr/bin/xauth" in /etc/ssh/ssh_config again I don't get the warning anymore. I haven't done any other config change apart from the XAuthLocation entry (which as I said I just commented out again to test this), so I'm not sure what caused the change of behaviour. I do regularly apply the lasted updates, but the openssh packages don't appear to have been updated recently. So I don't know what particular circumstance triggered the warning message, but since the config entry in /etc/ssh/ssh_config for XAuthLocation did solve the issue when it presented itself, it might still be a good idea to include it in the default /etc/ssh/ssh_config in the openssh-clients package.
I have the same issue when ssh'ing to my tablet. And the tablet doesn't even use Xorg.
CC: (none) => kristoffer.grundstrom1983
About a missing XAUTH for X11R6 thou. Don't know if that's valid in here to. If not, I'm sorry.
This is for Mageia 1.
(In reply to comment #6) > This is for Mageia 1. Hi Kristofer, Good that you tell your issue is about Mageia 1. Even if it were exactly the same issue, when it affects a different release it should go into a seperate bug report. When you are not sure your issue is a bug, please visit https://forums.mageia.org/en/viewforum.php?f=6 for support first. ******* This bug couldn't be reproduced in Cauldron, therefore I'm closing it
Status: NEW => RESOLVEDCC: (none) => m.van.waesResolution: (none) => INVALID