Ubuntu :: System Will Not Accept Password At Unlock
Nov 29, 2010
I recently did a clean install of Maverick Meerkat and copied a few configuration files from my old system. I can log on normally, and the system works just fine. However, when I lock the workstation with any method, the system will not accept my password. I'm certain that I'm typing it correctly (I tried over 20 times) and that the capslock is not on. When I reboot, I can log in again just fine. In other words, my password only works at initial login, not when unlocking the workstation.
I am using Ubuntu 10.10. I like to change the Lockscreen which appears when i need to enter my password to unlock the system. Currently it is apppearing fully black.
I am trying to be a super user in terminal but I can't. I am sure that I type the correct password, I check also the caps lock button and the language. Also I can't go to the yast. note that the root password is exactly the same as user password
Code: nobani@linux-m9c6:~> su Password: Permissions on the password database may be too restrictive. su: incorrect password nobani@linux-m9c6:~> I am using KDE 4.3.5 on openSUSE11.2
I am using a ubuntu 10.10 desktop,i cannot login to my system it doesnt accept the password. when i login in safe mode i get through but when i run any command i get segmentation fault.
I've tried Ubuntu, Arch, and most recently Fedora but the SUSE GNOME environment blows everything else away!
The only problem (so far) is that Network Manager requires you to enter your password every time you login to unlock the password keyring. I want to disable this.
I think some distros disable the prompt by using the login password to unlock the keyring, but I use auto-login (if that makes a difference).
I'm using Ubuntu 10.04LTS. I'm trying to configure my chat accounts. But after entering username and password, it is asking "Enter password to unlock your login keyring". I have entered my login password. But it is saying that "The password you use to log in to your computer no longer matches that of your login keyring."
i set my pass on ubuntu 10.4 and it work so good on installing app but suddenly it stopped working i thought i would restart my pc i tried to inter my pass again ubuntu don't accept it although it's surely true
I have this issue on both Ubuntu and Lubuntu 11.04 64-bit on 2 different machines. I have not tested 32-bit.
When I run synaptic or update-manager it presents me with gksu, not gksudo as it previously did in previous Ubuntu releases, no matter how many times I try it will not accept my password.
I have even given it command line arguments to print the password to the terminal and it's correct.
I have found a workaround - by running gksu-properties and changing the mode from su to sudo it will now display gksudo and accept my password.
However, I want to know why it won't accept my sudo password for the su and gksu commands? There are no error messages which are outputted, the gui just says incorrect password.
I just re-sized my windows partition on my laptop and installed 10.04.1. Brand new clean install. I set up my user account, gave it a password, and everything was fine until I tried to connect to my wireless. I typed in the security key for my wireless, and it asked for a password to unlock the default keyring. The problem is, I never set a password for the "default" keyring. I never changed my user password. I didn't auto-login, I entered my password. This was the first boot up of the machine after installing 10.04.1. I can't use Empathy, because the keyring cannot be unlocked. If I "cancel" it gives me an error saying the account details are wrong, but I log into my facebook, aim, and msn every day, so I know the passwords are correct.
I have read about other issues with the keyring and with the auto-login bug that is associated with it. I have also read up on the bug that occurs with that as well. I couldn't find anything about my specific situation, so I hope this isn't a re-post of an issue that has already dealt with, but I did look it up. If it helps, the laptop I am running is a HP Pavilion dv7-3065dx, and I have Ubuntu Desktop 10.04.1 x86 installed. Clean install and the only thing I have done was log in, connect to network, and try to set up Empathy. Both Empathy, and connecting to network, gave me the issues with the keyring. It appears that there is already a password for the default keyring, it is not blank, and my user login password does not work for it. I'm at a loss...
Since upgrading to Meerkat, I have been getting a pop-up window with the message "Enter password to unlock the private key" every time I attempt to ssh into a server that does NOT use password authentication. I know some people like the remember password "feature", but I prefer just a plain unadulterated ssh session in a terminal. Does anyone know how to stop this message?
So far I have unsucessfully tried:
None of the above worked - and I was sure to log out and back in before testing the behavior.
using ubuntu 10.10.. firsly it was asking me for password when i open my computer but i disabled that option and now it doesnt ask me.. but there is something else.. the desktop appear.. and i receive a message like i have to enter password to unlock the login keyring something like that.. can somebody explain me why? what can i do to stop this? i can actually use the computer open folders do anything but the password box keep appearing.
I just reinstalled ubuntu lucid after accidentally damaging it, And I used all the same passwords and user names as before, I can login fine, and I can do sudo commands, but the gnome keyring wont accept my password, I tried changing my password using Applications>accessories>Passwords and encryption but that didn't work. How can I fix this so that keyring will accept my password, I need it to save my wireless router password.
For some reason, several irksome changes have occurred. The worst is that it won't let me log in. It will not accept my password.? I was told that if I downloaded Ubuntu, I could use that to get to control panel and fix the problem. After 4.5 hours on another pc, I had the download and the cd does boot Ubuntu. What is my next step I have no working knowledge of Ubuntu.
I have an Ubuntu 10.10 box authenticating Users against an LDAP server. User authentication works fine - ssh, console or Gnome.
The only place it has an issue is when the gnome-screensaver is activated and locks the computer. When I try to enter the correct password at this point I get these error in the logs;
Dec 20 14:42:23 box-ubuntu unix_chkpwd[12240]: password check failed for user (myname) Dec 20 14:42:23 box-ubuntu gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=10038 euid=10038 tty=:0.0 r user= rhost= user=myname Dec 20 14:42:23 box-ubuntu gnome-screensaver-dialog: pam_ldap(gnome-screensaver:auth): Authentication failure; user=myname
After not using Ubuntu for a couple of weeks - suddenly it will no longer accept my username or password- it does not say which one it doesn't like - been using the same ones for 3 years.How can I get in to reset ?It is on a multiboot PC... Ubuntu/WinXP Pro/Win XP home MTIA
I'm experimenting with the passwd command to become more failure it.created an user account that had no password to practice on. I tried using the -u option to unlock it go the response:Cannot unlock the password for 'duplicateTest'!Read the man page and it instructs me to add the -f option to force it to accept unlocking an account with no password but !. I type in:passwd -uf duplicateTestThe response is:passwd: invalid option-- 'f'I rearranging the options and it prompted me to enter a change of finger information. Tried separating them, bracketing them ect...no dice.Can't find anything else on the net but what is stated on the man page, to add the force option.
I have recently made a fresh install of Lucid Lynx. After restarting my computer (due to kernel updates), my log in password no longer unlocks my login keyring. I have never changed either password, so there is no "old" password to resort to.How do I fix this? I am not opposed to deleting whatever data is encrypted by this keyring. Also, how might this have happened? This could be a bug; are there any relevant log files or such?
I just set up my Debian 8.3.0 Jessie install a couple of days ago. Today I am having a problem carrying out a command in terminal. All I want to do at the moment is make sure my firewall is active. I log in and out of my computer using the password that I set when I originally installed Debian, and I use the same password in the package updater, but today it would not accept that password in terminal. Here is what I am seeing;
rocky@debian:~$ sudo ufw-enable [sudo] password for rocky: rocky is not in the sudoers file. This incident will be reported. rocky@debian:~$ sudo ufw-enable [sudo] password for rocky: Sorry, try again. [sudo] password for rocky:
The asterisk I downloaded came with Centos 5.3 It runs well on VM console But the problem is when It request for localhost login which accepts input but the password does not accept input at all.
I have recently installed CentOS 5.4. I went ahead and enabled encryption for the root partition. everything was fine for the first few days, but today it started refusing my password on boot. The weird thing is after refusing the password several times it accepted it once, then when I rebooted to test refused the password it had accepted moments earlier. I guessed the password file got corrupt or something so I did a clean install. During the install it asked for the password to access the partition and accepted (!) the password. I went ahead and deleted the old partition and reinstalled from scratch just to be sure. And I made extra certain I put in the correct password with no fumble fingers. Sure enough the blasted thing refuses the password I just created during boot. However, if I input the password into the setup it accepts it. What the hell is going on here?
I'm using 9.10 most recent updates. I want to connect to a wireless network and get a dialog box offering "WPA & WPA2 personal" as the only choice. The passphrase I was given is 6 letters but the "Connect" button does not light up until I get to 8 when entering wpa/wpa2.
Do I need to convert the passphrase somehow?
Atheros 9k and Linksys "Wirelss G router with SRX200".
I had 9.04 64-bit with / and /home in separate partitions. Today I used 10.10 alternate install to install a command line system. Then installed gnome-core, synaptic, gparted, and a few other things. Now when I go to System > Administration > Synaptic Package Manager or to Gparted, I am asked for the "administrator password". I type in my password, but it is not accepted. However, from a terminal I can "sudo synaptic", give my password, and install whatever I want.
It's a pretty weird issue I'm having, when I need to provide access for a command in terminal IE: something using sudo, it just doesn't accept text. I thought it might be my keyboard at first (g15) but I tried copying and pasting the password into there and it just wouldn't do anything except for remain blank
I just did a fresh install of 11.4 My system auto-logs in and I know there's a bug in seahorse that doesn't like that method.
Anyway, I tried to unlock my "Passwords: login" in seahorse, but it won't budge.
The details about this user are that I re-used an 11.3 /home/$user directory. Could that be the reason? I logged out of the Desktop and back in using my password manually. I can sudo with my password. I can change the system with my password everywhere except in seahorse. The password is exactly the same in 11.4 as it was in 11.3.
The .gnupg/ directory is 600 and its contents are all 600 except for agent.info which is 644.
Following a year old post, I got this from shell code...
I'm still fairly new to Suse(and Linux) I have an account on my system that is locked when i run passwd -S accountname i get 'accountname lk' as the response. However when i try to unlock it using passwd -u accountname i get 'Cannot unlock the password for accountname!'.Any ideas on why i can't unlock the account?
