Despite trying numerous methods, my laptop goes to sleep over and over

My laptop will randomly go to sleep and then it will not wake up unless i remove the battery and wait. It usually only does this when I leave it alone, but often it does it when I’m in the middle of writing, scaring me a lot. My battery is at 100% so it is not an issue of running out of battery.

This is a lenovo thinkpad.

I have disabled all of the sleep and hibernation settings in the GUI.

I have turned off hibernation and sleep with the mask command after following several guides here.

I have downloaded and installed the extension caffeine and made sure its enabled and in my startup.

It absolutely won’t go back up if the battery stays in?
:thinking:

Sounds like your battery is dead, Jim.

1 Like

Please define sleep.

Is it suspend (what would happen when closing the lid), hibernation or does the screen only turn off? If it doesn’t come back, how do you know what happened?

You could read the journal from the last boot with journalctl -b -1 --no-pager, go to the bottom and post the last 50 (or so) lines.

I’ll try replacing the battery and then will get back to you

Maybe also try cleaning the battery contacts on battery and system. Because, yes, you may say/feel the battery’s at 100% but it seems the system as such doesn’t agree when it powers down.

1 Like

By sleep I mean that it remembers all the applications and doesn’t close them (so for example I don’t lose my files open in vim). The screen is black and the power button does nothing. Removing the battery and then putting it back in will let it “turn on” and all my applications are still open. It does actually have to turn on and through the booting process. Its not as if the screen just goes black and nothing changes.

Ah. I know what happened because it only turns back on after I remove the battery. Here are the last 50 or so lines.

Nov 26 14:37:50 Journal systemd[487]: Started Dolphin - File Manager.
Nov 26 14:37:50 Journal plasmashell[630]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:433: Unable to assign [undefine
d] to QString
Nov 26 14:38:16 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:16 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:18 Journal firefox[1231]: [2022-11-26T19:38:18Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:18 Journal firefox[1231]: [2022-11-26T19:38:18Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:18 Journal firefox[1231]: [2022-11-26T19:38:18Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:18 Journal firefox[1231]: [2022-11-26T19:38:18Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:18 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:18 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:18 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:18 Journal rtkit-daemon[561]: Supervising 7 threads of 4 processes of 1 users.
Nov 26 14:38:19 Journal rtkit-daemon[561]: Successfully made thread 1560 of process 1231 owned by '1000' RT at priority 10.
Nov 26 14:38:19 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:38:20 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:38:20 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:38:22 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:38:22 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:38:23 Journal firefox[1254]: [2022-11-26T19:38:23Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:23 Journal firefox[1254]: [2022-11-26T19:38:23Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:23 Journal firefox[1254]: [2022-11-26T19:38:23Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:38:23 Journal firefox[1254]: [2022-11-26T19:38:23Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:42:07 Journal manjaro-hello[758]: Info: Gnome-layout-switcher not installed
Nov 26 14:42:07 Journal systemd[487]: app-manjaro\x2dhello@autostart.service: Consumed 2.552s CPU time.
Nov 26 14:42:32 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:42:32 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:44:02 Journal NetworkManager[330]: <info> [1669491842.1891] device (wlp3s0): set-hw-addr: set MAC address to 16:AF:AA:55:AB:76 (scanning)
Nov 26 14:44:02 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:44:02 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:44:02 Journal NetworkManager[330]: <info> [1669491842.5885] device (wlp3s0): supplicant interface state: disconnected -> interface_disabled
Nov 26 14:44:02 Journal NetworkManager[330]: <info> [1669491842.5998] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Nov 26 14:44:40 Journal dbus-daemon[320]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' re
quested by ':1.73' (uid=0 pid=1845 comm="sudo systemctl mask sleep.target suspend.target hi")
Nov 26 14:44:40 Journal dbus-daemon[320]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.ho
me1.service not found.
Nov 26 14:44:40 Journal sudo[1845]: pam_systemd_home(sudo:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 26 14:44:43 Journal audit[1845]: USER_AUTH pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock ac
ct="micahjava" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal audit[1845]: USER_ACCT pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="micahjav
a" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal sudo[1845]: micahjava : TTY=pts/1 ; PWD=/home/micahjava ; USER=root ; COMMAND=/usr/bin/systemctl mask sleep.target suspend.target hi
bernate.target hybrid-sleep.target
Nov 26 14:44:43 Journal audit[1845]: CRED_REFR pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="roo
t" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal kernel: audit: type=1100 audit(1669491883.619:63): pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_failloc
k,pam_permit,pam_faillock acct="micahjava" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal kernel: audit: type=1101 audit(1669491883.619:64): pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_pe
rmit,pam_time acct="micahjava" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal kernel: audit: type=1110 audit(1669491883.619:65): pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_p
ermit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal kernel: audit: type=1105 audit(1669491883.619:66): pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_systemd_h
ome,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal audit[1845]: USER_START pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam
_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal sudo[1845]: pam_unix(sudo:session): session opened for user root(uid=0) by micahjava(uid=1000)
Nov 26 14:44:43 Journal systemd[1]: Reloading.
Nov 26 14:44:43 Journal audit: BPF prog-id=18 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=19 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=20 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=21 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=22 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:67): prog-id=18 op=LOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:68): prog-id=19 op=LOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:69): prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:70): prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:71): prog-id=20 op=LOAD
Nov 26 14:44:43 Journal kernel: audit: type=1334 audit(1669491883.859:72): prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=23 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=24 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=25 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=26 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=27 op=LOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit: BPF prog-id=0 op=UNLOAD
Nov 26 14:44:43 Journal audit[1845]: USER_END pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_
permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal audit[1845]: CRED_DISP pid=1845 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="roo
t" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:44:43 Journal sudo[1845]: pam_unix(sudo:session): session closed for user root
Nov 26 14:45:01 Journal polkitd[322]: Registered Authentication Agent for unix-process:1922:47249 (system bus name :1.75 [/usr/bin/pkttyagent --notify-fd 5
--fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 26 14:45:01 Journal systemd-logind[327]: Unit hibernate.target is masked, refusing operation.
Nov 26 14:45:01 Journal polkitd[322]: Unregistered Authentication Agent for unix-process:1922:47249 (system bus name :1.75, object path /org/freedesktop/Pol
icyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Nov 26 14:46:20 Journal dbus-daemon[320]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' re
quested by ':1.76' (uid=0 pid=1990 comm="sudo ls")
Nov 26 14:46:20 Journal dbus-daemon[320]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.ho
me1.service not found.
Nov 26 14:46:20 Journal sudo[1990]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Nov 26 14:46:20 Journal audit[1990]: USER_ACCT pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="micahjav
a" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal sudo[1990]: micahjava : TTY=pts/1 ; PWD=/etc/systemd ; USER=root ; COMMAND=/usr/bin/ls
Nov 26 14:46:20 Journal audit[1990]: CRED_REFR pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock a
cct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal sudo[1990]: pam_unix(sudo:session): session opened for user root(uid=0) by micahjava(uid=1000)
Nov 26 14:46:20 Journal audit[1990]: USER_START pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam
_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal kernel: kauditd_printk_skb: 16 callbacks suppressed
Nov 26 14:46:20 Journal kernel: audit: type=1101 audit(1669491980.939:89): pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_pe
rmit,pam_time acct="micahjava" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal kernel: audit: type=1110 audit(1669491980.939:90): pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_p
ermit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal kernel: audit: type=1105 audit(1669491980.939:91): pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_systemd_h
ome,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal sudo[1990]: pam_unix(sudo:session): session closed for user root
Nov 26 14:46:20 Journal audit[1990]: USER_END pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_
permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal audit[1990]: CRED_DISP pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock a
cct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal kernel: audit: type=1106 audit(1669491980.949:92): pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_systemd_
home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:46:20 Journal kernel: audit: type=1104 audit(1669491980.949:93): pid=1990 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_p
ermit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Nov 26 14:48:47 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:47 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:49 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:49 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:49 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:49 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:51 Journal firefox[1773]: [2022-11-26T19:48:51Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:48:51 Journal firefox[1773]: [2022-11-26T19:48:51Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:48:51 Journal firefox[1773]: [2022-11-26T19:48:51Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:48:51 Journal firefox[1773]: [2022-11-26T19:48:51Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Nov 26 14:48:51 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:51 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:51 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:51 Journal rtkit-daemon[561]: Supervising 8 threads of 5 processes of 1 users.
Nov 26 14:48:51 Journal rtkit-daemon[561]: Successfully made thread 2309 of process 1773 owned by '1000' RT at priority 10.
Nov 26 14:48:51 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:48:54 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:48:54 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:02 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:02 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:06 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:06 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:30 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:49:30 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:50:51 Journal NetworkManager[330]: <info> [1669492251.1908] device (wlp3s0): set-hw-addr: set MAC address to EE:2C:50:03:40:E4 (scanning)
Nov 26 14:50:51 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:50:51 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:50:51 Journal NetworkManager[330]: <info> [1669492251.5878] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Nov 26 14:50:51 Journal NetworkManager[330]: <info> [1669492251.6034] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Nov 26 14:51:53 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:51:53 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:21 Journal systemd[1]: Starting Cleanup of Temporary Directories...
Nov 26 14:52:22 Journal systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Nov 26 14:52:22 Journal systemd[1]: Finished Cleanup of Temporary Directories.
Nov 26 14:52:22 Journal audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/sys
temd/systemd" hostname=? addr=? terminal=? res=success'
Nov 26 14:52:22 Journal audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/syst
emd/systemd" hostname=? addr=? terminal=? res=success'
Nov 26 14:52:22 Journal kernel: audit: type=1130 audit(1669492342.039:94): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm=
"systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 26 14:52:22 Journal kernel: audit: type=1131 audit(1669492342.039:95): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm=
"systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 26 14:52:31 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:31 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:33 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:33 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:36 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:36 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:36 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:36 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:37 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:37 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:37 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:37 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:38 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:38 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Successfully made thread 2845 of process 2675 owned by '1000' RT at priority 10.
Nov 26 14:52:41 Journal rtkit-daemon[561]: Supervising 10 threads of 7 processes of 1 users.
Nov 26 14:54:22 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:54:22 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 14:57:39 Journal NetworkManager[330]: <info> [1669492659.1959] device (wlp3s0): set-hw-addr: set MAC address to 82:D4:D6:3E:DB:F7 (scanning)
Nov 26 14:57:39 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:57:39 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 14:57:39 Journal NetworkManager[330]: <info> [1669492659.5972] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Nov 26 14:57:39 Journal NetworkManager[330]: <info> [1669492659.6100] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Nov 26 15:01:01 Journal CROND[2962]: (root) CMD (run-parts /etc/cron.hourly)
Nov 26 15:01:01 Journal CROND[2961]: (root) CMDEND (run-parts /etc/cron.hourly)
Nov 26 15:01:18 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 15:01:18 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 15:04:28 Journal NetworkManager[330]: <info> [1669493068.1907] device (wlp3s0): set-hw-addr: set MAC address to 8E:48:32:E3:B0:44 (scanning)
Nov 26 15:04:28 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 15:04:28 Journal kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Nov 26 15:04:28 Journal NetworkManager[330]: <info> [1669493068.5880] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
Nov 26 15:04:28 Journal NetworkManager[330]: <info> [1669493068.6035] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
Nov 26 15:06:05 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.
Nov 26 15:06:05 Journal rtkit-daemon[561]: Supervising 9 threads of 6 processes of 1 users.

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

Yeah it will not under any circumstances.

  • “Sleep” mode saves your computers state in RAM only, and RAM ofcourse needs power to keep it’s contents.
  • “Hibernate” is same as sleep with difference that it saves the state to the disk instead of the RAM,
    You can easily tell the diff, because when it hibernates you will notice quite a lot of disk access followed by your systems noise becoming silent. (fans turn off etc)

What you describe there is called “hibernation”, because it can only bootup from “power-off” state and keep all your apps open when it has saved that info on disk.

When your screen goes black and won’t turn back on, even with the power button, it just means IMHO that your system either went into “sleep” or “sleep-then-hibernate” mode.

When it’s just “sleep” mode but screen won’t turn back on when you wake it by moving your mouse or pressing any key; Then it doesn’t properly re-initializes your gfx card when you try to wake it :woman_shrugging:

(I haven’t looked at any logs you posted)

1 Like

Thank you for explaining that to me. :slight_smile:

I came back from bed and it didn’t hibernate on me yet this morning. It usually only takes a few hours so perhaps I will get lucky today lol.

The issue still persists and I have no idea how to even approach this issue

Note most specifically Yochanan’s reply as to the battery seemingly just being kaput, and if so lucky, mine as to cleaning (best with a bit of alcohol) contacts between system and battery. Because it very much appears to be hardware; failure to communicate between battery and system at least.

Thanks. I cleaned it out and replaced the battery. It continued to do the exact same thing, and I had no idea what to do. The problem ended up being solved with caveman methods. I beat it into submission with a sledge hammer and set what was left on fire. Before hand, I took the ram, hard drives, and screen to be salvaged for other projects. I also disposed of the battery the proper way.

I am now on a fresh laptop using its ram and components. Problem has been solved.

Wouldn’t it be funny if it now turned out to be its RAM…

Oh god that would be like a horror movie