All of a sudden I am getting the this message "Unlock keyring 'Default An application wants access to the keyring ‘Default’ but it is locked.
Any ideas 'cos it’s driving me nuts. >:(
Ubuntu 10.10 for netbook, booted from dongle, Samsung NX10
If you are running from a LiveUSB (ie. you get offered the option to “Try Ubuntu” or “Install Ubuntu” during the boot process)
Auto login will be enabled by default… It’s most likely the wireless connection that wants the keyring password.
Easiest way round this is to delete your current wireless connection in network manager, then recreate it… but when asked for a “Keyring Password”… leave it blank… it will complain about “Unsafe Storage”, but accept it anyway.
AFAIK, the Ubuntu LiveCD / LiveUSB uses the following login account by default:
Username = ubuntu
Password =
with auto login enabled.
So you probably typed in a keyring password of your own whilst setting up your wireless connection…
Correct Mark, that’s exactly what I have done. Once again many thanks.
Adam
I changed my password and for the keyring it keeps asking for the old one (which I do) to connect to Wifi. I tried the fix Ubuntu lists in help, but it didn’t work (sorry don’t remember). I just started another Wifi but it never resets. It’s somewhat annoying having to enter it again and again. I’ve got 60 or so Wifi’s - I don’t want to delete them.
Open a terminal (Ctrl+Alt+T) and run this command:
mv -v ~/.gnome2/keyrings/default.keyring ~/.gnome2/keyrings/default.keyring.old
Expected output from that command =
'/home//.gnome2/keyrings/default.keyring' -> '/home//.gnome2/keyrings/default.keyring.old'
If that command runs without error … REBOOT.
When your system restarts, you will be prompted by “Authentication required by wireless network” … enter your WEP or WPA key, and click the “Connect” button.
You will THEN be prompted to “Choose password for new keyring” … leave BOTH fields BLANK (or use your current login password), and click the “OK” button.
You will then be warned about “Store passwords unencrypted?” … click the “Use Unsafe Storage” button.
You should not be prompted for a keyring password for wireless again. 
It did this.
mako4@mak4-laptop:~$ mv -v ~/.gnome2/keyrings/default.keyring ~/.gnome2/keyrings/default.keyring.old
mv: cannot stat /home/mako4/.gnome2/keyrings/default.keyring': No such file or directory mako4@mak4-laptop:~$ sudo su [sudo] password for mako4: root@mak4-laptop:/home/mako4# mv -v ~/.gnome2/keyrings/default.keyring ~/.gnome2/keyrings/default.keyring.old mv: cannot stat /root/.gnome2/keyrings/default.keyring’: No such file or directory
root@mak4-laptop:/home/mako4#
Which verson of Ubuntu are you using ?
What is the output from:
ls -a ~/.gnome2/keyrings
Ubuntu 10.4.1 AMD64
THis is output: . … login.keyring user.keystore user.keystore.SIAANV
OK, let’s rename the WHOLE ~/.gnome2/keyrings directory:
(it will get recreated on next login)
mv -v ~/.gnome2/keyrings ~/.gnome2/keyrings.old
Expected output:-
`/home//.gnome2/keyrings' -> `/home//.gnome2/keyrings.old'
If that command runs without error … REBOOT.
When your system restarts, you will be prompted by “Authentication required by wireless network” … enter your WEP or WPA key, and click the “Connect” button.
You will THEN be prompted to “Choose password for new keyring” … leave BOTH fields BLANK (or use your current login password), and click the “OK” button.
You will then be warned about “Store passwords unencrypted?” … click the “Use Unsafe Storage” button.
You should not be prompted for a keyring password for wireless again.
It didn’t show the last “/keyring”, JUST
/home/<username>/.gnome2/keyrings' -> /home//.gnome2/keyrings.old
Yup that was a typo … I seem to be making a few of those lately :o
(fixed in original posting)
But did it sort your keyring problem ?
I guess, but it never asked for anything about “choosing password for new keyring”, or “store unencrypted”… only password for Wifi. Wait, let’s disconnect and reconnect. Yeah, thanks, doesn’t ask for anything more, but do I still have normal security for Wifi? Like the idea of encrypted passwords for WiFi.
If you haven’t had to re-enter the keyring password, it must have picked up the login password … which is encrypted.
You know I “fixed” file system on that 4gb USB jumpdrive on Windows, but it’s gone back to read only again (something about netbook maybe). Whats the Linux command to just force it to all be writeable?
With the USB stick plugged in and mounted, what;s the output from:
mountincluding the prompt line.
/dev/sda9 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
gvfs-fuse-daemon on /home/mako4/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=mako4)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/dev/sdb on /media/PEPPERMINT type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)
/dev/sda1 on /media/ACER-NEW type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)
/dev/sda2 on /media/DATA3-ntfs type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)
OK, navigate to -
/media
Now tell me which directory in there is the USB stick ? … is it /media/PEPPERMINT ?
Can you also tell me your username, or show me your command line prompt … such as:-
mark@AA1-Blue ~ $
Yes- stick is: /dev/sdb on /media/PEPPERMINT type vfat
or do you mean on file manager (same)
mako4@mak4-laptop:~$
Why?
sudo chown -R mako4:mako4 /media/PEPPERMINT
That will recursively take ownership of the mount point.
Does that make it WRITABLE?? Seems that instruction needs a few more letters- it redid every file saying only read, and still doesn’t write, copy, or save anything new.