Here is some information from the auth.log
First attempt when opening the network settings:
May  7 01:30:09 myname sudo: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May  7 01:30:09 myname sudo: PAM [error: /lib/security/pam_smbpass.so: cannot 
open shared object file: No such file or directory]
May  7 01:30:09 myname sudo: PAM adding faulty module: 
/lib/security/pam_smbpass.so
May  7 01:30:20 myname sudo: user : TTY=unknown ; PWD=/home/user ; USER=root ; 
COMMAND=/usr/bin/network-admin
May  7 01:30:20 myname sudo: pam_unix(sudo:session): session opened for user 
root by (uid=0)
May  7 01:30:20 myname sudo: pam_unix(sudo:session): session closed for user 
root

Second attempt in user and group settings, I can't work on group settings on my 
home user name, see screenshot no.3
Then marking root and unlock to work on group settings, then password and 
pressing authenticate, the messages are:
May  7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM unable to 
dlopen(/lib/security/pam_smbpass.so)
May  7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM [error: 
/lib/security/pam_smbpass.so: cannot open shared object file: No such file or 
directory]
May  7 01:45:17 myname polkit-grant-helper-pam[5966]: PAM adding faulty module: 
/lib/security/pam_smbpass.so
May  7 01:45:28 myname polkit-grant-helper[5963]: granted authorization for 
org.freedesktop.systemtoolsbackends.set to pid 5933 [uid=1000] [auth=user]

Third attempt to open group settings: success
Why, after typing the password I didn't press authenticate, I just pressed 
enter and every window from user and root is available to scroll and work with.

Network administration is still not. And I have no idea what therefore
has to be changed.


** Attachment added: "screenshot3"
   http://launchpadlibrarian.net/14300146/Groupsettings.png

-- 
After upgrading from gutsy to hardy, all controls in "Network Settings" window 
are greyed out, making it impossible to configure networking.
https://bugs.launchpad.net/bugs/227383
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to