Summary: | net-misc/neatx su/ssh authentication | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan de Konink <stefan> |
Component: | [OLD] Server | Assignee: | Gentoo NX Server project <nx> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 93nt00r0ck5, tshchik |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan de Konink
2009-11-09 13:14:33 UTC
Nov 9 14:11:38 nemesis su[17064]: pam_authenticate: Permission denied nx cannot su to your normal user, probably pam related indeed Can you try to remove the nx user (and its home folder), and remerge neatx to recreate it? Then try something like this on the server # sudo -u nx bash (run shell as nx user) $ su - youruser and see what it reports (In reply to comment #1) > Nov 9 14:11:38 nemesis su[17064]: pam_authenticate: Permission denied > > nx cannot su to your normal user, probably pam related indeed > > Can you try to remove the nx user (and its home folder), and remerge neatx to > recreate it? Then try something like this on the server > # sudo -u nx bash (run shell as nx user) > $ su - youruser > and see what it reports > I was having the same problem as the OP. Adding the nx user to the wheel group worked for me. eg. (as root) gpasswd -a nx wheel NeatX works pretty well, but I have only just got it working. Doesn't play nice with my dual screen setup I have at work though. Ah thanks for pointing this out, I had not seen that this was with su authentication (which requires nx user in wheel group, as explained in postinstall log). nx user is not added by default to wheel group as other authentication methods and other NX servers do not need it (and allowing nx to run sudo when not needed is not a good idea) So working with nx user in wheel group, thanks for the report :) |