-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Liz,
another idea:
Are your regular users part of some central user administration system, like LDAP, a Microsoft Windows Domain or an Active Directory (either natively or emulated via SAMBA)?
In other words, are your systems set up in a way that a particular user account will automatically have permission to log in on several machines and that changing the password on one machine updates it on all the others?
- -->"root" is usually exempt from that and a local, per-machine account.
So if your users are centrally administered as described above, the behavior you are seeing would point to an issue with the authentication system in use at your site.
While X2Go uses SSH, it uses a different implementation of SSH than the regular SSH client, so a central authentication system expecting only a regular SSH connection might get confused.
Please also do follow "rpr"s advice in the previous message and check if your users have files named ".Xauthority*" in their home directories that aren't owned by them.
Note that the leading dot in the file name means they are hidden files, so the best way to check for them is: ls -lah ~/.Xauthority* from an SSH session of the user account in question.
Kind Regards, Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJWJ55zAAoJEG7d9BjNvlEZE9kH/jvEHj6fhEYQTgKFdbpMxCli gFk7WgN2MWoeA9P0b5whkXZfFSnmpO3sVyXf+TKOnuT2pvhU/2px5oJdvxmy10PC 14+NYJI363HeZwGxsEFTzNY5JPHRTVzW1p8O0+4UpiplevjiXondAqiPe1d1PW08 PsC58D98dlLxBRX6ShUJY+fOlCkbMipMy8FYppm5jFM6CzPO6XTmAkNRR/FyTz5S 0/OguVTc8R2jyFK3oTlj2p+nR5h6x3x03gSMv5OkW3YHSA1W6Wb3uEqdrYmKC7MO NQqZT3ds4w0Rg2J49N+e+GL/uvEhM/Be+beui9do4tcgYVIVCBssn4N4+NxRNCk= =KeyA -----END PGP SIGNATURE-----