Terminal memory loss regarding passwords. Arch Linux
Terminal memory loss regarding passwords. Arch Linux
sssssso. Theme: Breeze [GTK2/3/4] :osssssss/ osssso+++. Icons: breeze [GTK2/3/4] /ossssssss/ +ssssooo/- Font: Noto Sans (10pt) [GTK2/3/4] `/ossssso+/:- -:/+osssso+- Cursor: breeze (24px) `+sso+:-` `.-/+oso: Terminal: GNOME Console 48.0.1 `++:. `-/+/ Terminal Font: Adwaita Mono (11pt) .` `/ CPU: AMD Ryzen 5 5600X (12) @ 4.65 GHz GPU: NVIDIA GeForce RTX 3070 [Discrete] Memory: 1.86 GiB / 15.54 GiB (12%) Swap: 0 B / 4.00 GiB (0%) Disk (/): 79.54 GiB / 914.83 GiB (9%) - ext4 Local IP (wlp36s0): 192.168.12.166/24 Locale: en_US.UTF-8
Frankette44
05-16-2020, 09:12 PM #1after like 5-6 hours of my pc being on terminal just forgets my password, do not know why here is a neofetch -` beckham@archlinux .o+` ----------------- `ooo/ OS: Arch Linux x86_64 `+oooo: Host: MS-7B86 (5.0) `+oooooo: Kernel: Linux 6.15.2-arch1-1 -+oooooo+: Uptime: 25 seconds `/:-:++oooo+: Packages: 1117 (pacman), 32 (flatpak) `/++++/+++++++: Shell: bash 5.2.37 `/++++++++++++++: Display (LG ULTRAWIDE): 3440x1440 @ 60 Hz in 34" [External] `/+++ooooooooooooo/` DE: GNOME 48.2 ./ooosssso++osssssso+` WM: Mutter (Wayland) .oossssso-````/ossssss+` WM Theme: Breeze -osssssso. sssssso. Theme: Breeze [GTK2/3/4] :osssssss/ osssso+++. Icons: breeze [GTK2/3/4] /ossssssss/ +ssssooo/- Font: Noto Sans (10pt) [GTK2/3/4] `/ossssso+/:- -:/+osssso+- Cursor: breeze (24px) `+sso+:-` `.-/+oso: Terminal: GNOME Console 48.0.1 `++:. `-/+/ Terminal Font: Adwaita Mono (11pt) .` `/ CPU: AMD Ryzen 5 5600X (12) @ 4.65 GHz GPU: NVIDIA GeForce RTX 3070 [Discrete] Memory: 1.86 GiB / 15.54 GiB (12%) Swap: 0 B / 4.00 GiB (0%) Disk (/): 79.54 GiB / 914.83 GiB (9%) - ext4 Local IP (wlp36s0): 192.168.12.166/24 Locale: en_US.UTF-8
It fails when executing commands like "sudo" or "login." You're trying to perform an action that needs authentication but isn't receiving a password response. Neofetch serves as a high-level system overview and display tool, offering limited practical value for troubleshooting.
Consider checking error logs in journalct for clues. Try commands like sudo journalctl --since=today -xe or grep specific terms such as "auth", "pam", "sudo", "pwd", or "login". These will highlight recent audit-related activity from today. Search for entries mentioning "audit", "sudo", "systemd-logind", or "pam". Look for lines indicating password issues, authentication failures, or system events around the time you suspect the problem occurred. Adjust the filter to narrow the scope if needed.
Couldn't find logs from June 15. I opened the gnome logs app here is what appeared. The entry at 2:44:55 AM says activation failed for 'org.freedesktop.nm_dispatcher'. There were also issues with duplicate names and service files not loading properly, plus a GDM and DBus error around that time.
The situation appears normal, though it isn't tied to authentication issues. It's recommended to review the logs during each occurrence and modify the "--since" parameter to something like "--since=-5m" to capture the last five minutes of activity before the failed login attempt.