Description of problem: user@host$ ssh root@remote_host root@remote_host's password: Last login: some time ago [root@remote_host]# system-config-securitylevel & [1] 31415 X11 connection rejected because of wrong authentication. The application 'system-config-securitylevel.py' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. [root@remote_host]# xclock [root@remote_host]# In other words, system-config-securitylevel gives that error, whereas a simple X app works as it should. In fact, several other system-config-... scripts produce the same error. I suspect it has something to do with the userhelper (or similar) wrapper. Version-Release number of selected component (if applicable): openssh-4.3p2-10 How reproducible: Always Steps to Reproduce: 1. See above Actual results: See above error message Expected results: I should be able to run system-config-* by logging onto a system as root with ssh X11 forwarding. Additional info:
P.S. & FWIW: SElinux is permissive on both computers - both are FC6.
I cannot reproduce this on fully updated FC6. Reassigning to usermode where the problem most probably is.
This might be a duplicate of #187637, please do the following to gather more information: * log in to the remote host * verify xclock works and s-c-securitylevel doesn't * Run the following command and report its output: (echo DISPLAY=$DISPLAY; echo XAUTHORITY=$XAUTHORITY; echo hostname=$(uname -n); xauth -n list) * While still logged on the remote host, run (su -) and check whether xclock works.
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.