terminal forgetting passwords. archlinux

[Ihavesmallpp]

after 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.      :ssssssso.         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

 

[Alex Atkin UK]

42 minutes ago, Ihavesmallpp said:

after like 5-6 hours of my pc being on terminal just forgets my password, do not know why here is a neofetch

What do you mean exactly?  What specifically is happening?

[Ihavesmallpp]

12 hours ago, Alex Atkin UK said:

What do you mean exactly?  What specifically is happening?

i type in my password and it just does not work i reboot then it magically again works i dont know how i dont know why.

[NoLeafClover]

Under what circumstances does your password "not work"? When running "sudo" or "login"? What are you attempting to do that requires a password and is not being accepted?

 

As an aside, neofetch is a high level OS and hardware summary / show-off tool, none of the information is particularly useful for any sort of debug scenario.

[Ihavesmallpp]

3 hours ago, NoLeafClover said:

Under what circumstances does your password "not work"? When running "sudo" or "login"? What are you attempting to do that requires a password and is not being accepted?

 

As an aside, neofetch is a high level OS and hardware summary / show-off tool, none of the information is particularly useful for any sort of debug scenario.

sudo insatlling an app and it has u enter your password 2 times

[NoLeafClover]

2 hours ago, Ihavesmallpp said:

sudo insatlling an app and it has u enter your password 2 times

 The first thing I would suggest is to look at possible error log messages in journalct, i.e.

sudo journalctl --since=today -xe -q SYSLOG_FACILITY=4 SYSLOG_FACILITY=10

or

sudo journalctl --since=today | grep -E "auth|pam|sudo|pwd|login"

This will show any audit (incl authentication) messages from "today". Look for anything related to "audit", "sudo", "systemd-logind", and "pam". For example, the following lines show an incorrect password was entered:

Jun 16 21:16:01 XXXX unix_chkpwd[33537]: password check failed for user (YourUsername)
Jun 16 21:16:01 XXXX sudo[33527]: pam_unix(sudo-i:auth): authentication failure; logname=YourUsername uid=1000 euid=0 tty=/dev/pts/4 ruser=YourUsername rhost=  user=YourUsername
Jun 16 21:16:01 XXXX audit[33527]: USER_AUTH pid=33527 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="YourUsername" exe="/usr/bin/sudo" hostname=? addr=? t>

You can adjust "--since" to something more manageable, e.g. "--since=-30m" to only filter the log messages from the last 30 minutes.

 

This should hopefully give you some hints as to why "sudo" failed.

[Ihavesmallpp]

4 hours ago, NoLeafClover said:

 The first thing I would suggest is to look at possible error log messages in journalct, i.e.

sudo journalctl --since=today -xe -q SYSLOG_FACILITY=4 SYSLOG_FACILITY=10

or

sudo journalctl --since=today | grep -E "auth|pam|sudo|pwd|login"

This will show any audit (incl authentication) messages from "today". Look for anything related to "audit", "sudo", "systemd-logind", and "pam". For example, the following lines show an incorrect password was entered:

Jun 16 21:16:01 XXXX unix_chkpwd[33537]: password check failed for user (YourUsername)
Jun 16 21:16:01 XXXX sudo[33527]: pam_unix(sudo-i:auth): authentication failure; logname=YourUsername uid=1000 euid=0 tty=/dev/pts/4 ruser=YourUsername rhost=  user=YourUsername
Jun 16 21:16:01 XXXX audit[33527]: USER_AUTH pid=33527 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="YourUsername" exe="/usr/bin/sudo" hostname=? addr=? t>

You can adjust "--since" to something more manageable, e.g. "--since=-30m" to only filter the log messages from the last 30 minutes.

 

This should hopefully give you some hints as to why "sudo" failed.

could not see june 15 logs so i went into the gnome logs app here is the log.2:44:55 AM dbus-broker-lau: Activation request for 'org.freedesktop.nm_dispatcher' failed.
12:44:42 AM gdm: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Jun 15 10:59:49 PM dhclient: exiting.
Jun 15 8:52:26 PM dbus-broker-lau: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
Jun 15 8:52:26 PM systemd: Failed to start Application launched by gnome-session-binary.
Jun 15 8:52:25 PM dbus-broker-lau: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
Jun 15 8:52:25 PM gdm-session-wor: gkr-pam: unable to locate daemon control file
Jun 15 8:52:18 PM dbus-broker-lau: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service'
Jun 15 8:52:15 PM kernel:
Jun 15 8:52:14 PM kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Jun 15 8:52:14 PM kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Jun 15 8:52:14 PM kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP1.PTXH], AE_ALREADY_EXISTS (20240827/dswload2-326)

 

[NoLeafClover]

There's nothing unusual in the above, but they're also not authentication related.

 

I would suggest looking at the logs whenever the issue occurs again and adjusting "--since" to something like "--since=-5m" to give you a 5 minute slice of logs immediately preceding the failed password attempt.

[Ihavesmallpp]

well thank you guys for your help but for whatever reason my retarded ass deleted the udev folder and so i had to reinstall arch and that fixed the issue.