F5F Stay Refreshed Software Operating Systems Linux fails to accept password after one minute.

Linux fails to accept password after one minute.

Linux fails to accept password after one minute.

_
___Nightmare__
Junior Member
17
10-27-2016, 01:25 PM
#1
Hello, this situation is unusual. I can access my computer and enter my password normally, but after a short time it stops working. When I log out and try again, it blocks me. After rebooting, it functions again, yet the password fails afterward. I tried checking the .Xauthority owner and used passwd, but no help was found. The shadow file is secure. I ran an update with sudo pacman -Syu. My system details: OS is ArcoLinux dualboot with Windows 10 (used occasionally for school). Device: Surfacelaptop 2-3, a model I own.
_
___Nightmare__
10-27-2016, 01:25 PM #1

Hello, this situation is unusual. I can access my computer and enter my password normally, but after a short time it stops working. When I log out and try again, it blocks me. After rebooting, it functions again, yet the password fails afterward. I tried checking the .Xauthority owner and used passwd, but no help was found. The shadow file is secure. I ran an update with sudo pacman -Syu. My system details: OS is ArcoLinux dualboot with Windows 10 (used occasionally for school). Device: Surfacelaptop 2-3, a model I own.

F
FastCat123
Member
55
10-28-2016, 05:34 AM
#2
No, the issue remains unchanged when you create a second account.
F
FastCat123
10-28-2016, 05:34 AM #2

No, the issue remains unchanged when you create a second account.

K
KidzBeEz
Member
242
11-04-2016, 06:28 PM
#3
At startup, the keyboard language may differ from the one used when the desktop loads. This could cause variations in behavior when entering the same password.
K
KidzBeEz
11-04-2016, 06:28 PM #3

At startup, the keyboard language may differ from the one used when the desktop loads. This could cause variations in behavior when entering the same password.

J
JZuli
Member
59
11-06-2016, 10:33 AM
#4
It remains the same keyboard. I've been using it for a while and haven't noticed any changes. It seems like there are no dead keys present.
J
JZuli
11-06-2016, 10:33 AM #4

It remains the same keyboard. I've been using it for a while and haven't noticed any changes. It seems like there are no dead keys present.

A
Amegahoney
Posting Freak
789
11-13-2016, 09:21 PM
#5
I set up a new user named test and added them to the wheel group. They functioned properly, handling updates and Vim editing of root files. I also tried logging back in using my account, which worked the same way.
A
Amegahoney
11-13-2016, 09:21 PM #5

I set up a new user named test and added them to the wheel group. They functioned properly, handling updates and Vim editing of root files. I also tried logging back in using my account, which worked the same way.

X
XxPvPxX2005
Junior Member
6
11-13-2016, 10:41 PM
#6
It remains the same keyboard. I've been using it for a while and haven't noticed any changes. It seems like there are no dead keys present.
X
XxPvPxX2005
11-13-2016, 10:41 PM #6

It remains the same keyboard. I've been using it for a while and haven't noticed any changes. It seems like there are no dead keys present.

S
S0w3y
Junior Member
7
11-15-2016, 04:09 PM
#7
I'm referring to the language preferences in the operating system and login interface. If the locale updates unexpectedly, you might type "qwertz" yet get "qwerty" displayed. When your password stops working, try opening a text editor and entering the password there to verify it. It's possible an older authentication script or method could lock your account if not handled properly. Checking logs with cat /var/run/faillock/<username> might help.
S
S0w3y
11-15-2016, 04:09 PM #7

I'm referring to the language preferences in the operating system and login interface. If the locale updates unexpectedly, you might type "qwertz" yet get "qwerty" displayed. When your password stops working, try opening a text editor and entering the password there to verify it. It's possible an older authentication script or method could lock your account if not handled properly. Checking logs with cat /var/run/faillock/<username> might help.

N
Nird_Bird
Member
165
11-15-2016, 05:21 PM
#8
Sorry, I should have separated those sentences. I’m not running in a second language. I read the Faillock manual carefully and followed the instructions. It wasn’t clear at first, but after resetting using another user’s guidance, it worked. Thank you for helping me through that. I didn’t realize files had man pages—it’s really surprising.
N
Nird_Bird
11-15-2016, 05:21 PM #8

Sorry, I should have separated those sentences. I’m not running in a second language. I read the Faillock manual carefully and followed the instructions. It wasn’t clear at first, but after resetting using another user’s guidance, it worked. Thank you for helping me through that. I didn’t realize files had man pages—it’s really surprising.

M
missyT1396
Member
189
11-17-2016, 03:46 PM
#9
Thank you for your message. I'm glad I could assist you.
M
missyT1396
11-17-2016, 03:46 PM #9

Thank you for your message. I'm glad I could assist you.