Comment 31 for bug 216990

On 05/07/2008 01:55 PM, Steve Langasek wrote:
> NoOp,
>
> On Mon, Apr 28, 2008 at 08:33:30PM -0000, NoOp wrote:
>
>> However, this will be an issue for those that upgrade from Gutsy to
>> Hardy (as I found out) and suddenly find that they can no longer log
>> into their machine via VNC. Perhaps a patch issuing new /etc/pam.d
>> /common-auth and /etc/pam.d/common-password with the pam_smbpass.so
>> related lines commented out would be a better solution?
>
> If you're unable to log in via VNC, then that's a much more serious error
> and one that's not at all explained by these log errors: the absence of
> this "optional" module should not cause any authentication failures, and it
> was on that basis that the change was made to enable this module.
>
> Please open a separate bug report about this issue and provide a link to it
> here. We will need to pin down this VNC problem, which may warrant rolling
> back the PAM config changes; the logging issue itself should be fixable with
> a small patch, but I currently have no explanation for why you would
> experience login failures with VNC that would be fixed by installing
> libpam-smbpass.
>

No clue. I just tested and it now seems to be fine.

To test I ensured that libpam-smbpass was not installed on the target
machine (this is the one with the Gutsy to Hardy upgrade), and that the
edited /etc/pam.d/common-auth and /etc/pam.d/common-password
pam_smbpass.so lines were un-commented (put them back). Rebooted the
target machine and now can VNC into it just fine; both from a Gutsy
machine and a fresh install (fully up to date) Hardy machine. Both using
the Terminal Server Client w/xvnc4viewer.

So, I can't seem to reproduce. Perhaps it was a case of VNC gremlins?
I'll wait until I upgrade another machine from Gutsy to Hardy and if I
can reproduce, then I'll file a separate bug.