9.04 Upgrade Caused Lost Permissions

[shawnpray]

I just upgraded from 8.10 to 9.04. I seem to have lost user and root privileges. I can log in, sometimes requiring two or three attempts with the same password, but when I try to use the Update Manager or any other program requiring root privileges, I am denied access. Neither my password nor the root password will get me anywhere. I placed my user in the root group and the root account is active and password protected. This is VERY frustrating. Any ideas?

[zvacet]

In recovery mode type


adduser username admin

username= your username

[shawnpray]

In recovery mode type


adduser username admin

username= your username
Thanks. I went in via recovery mode and it stated my user was already part of the admin group. I think the error may have to do with the fingerprint reader I have and I installed thinkfinger a few versions ago (8.04). So far i can log in and use root-required apps if I use the fingerprint reader but if I try to enter my password, it is not recognized. Any ideas?

[prizrak]

Thanks. I went in via recovery mode and it stated my user was already part of the admin group. I think the error may have to do with the fingerprint reader I have and I installed thinkfinger a few versions ago (8.04). So far i can log in and use root-required apps if I use the fingerprint reader but if I try to enter my password, it is not recognized. Any ideas?

I had that problem, it has to do with the common-auth file in /etc/pam.d
I'm assuming you had the same set up as mine. Try pasting this into
/etc/pam.d/common-auth
NOTE: It will break your fingerprint reader functionality but will make passwords work. I'm still looking for a way to get both working :)

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules. See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth [success=1 default=ignore] pam_unix.so nullok_secure
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_smbpass.so migrate
# end of pam-auth-update config