Sometimes, after using the computer for a while, when I shut it down screen turns off but keyboard backlight keeps on and I need to force the shutdown using the power button (which is not recommended).
It happens when I use the PC for a while, if I boot it and shut it down after a few minutes, normally, it shuts down properly.
While no one else has replied yet, I’ll throw these thoughts out.
When I installed EOS, I disabled hibernating. The OS is so fast, I don’t need it to hibernate. I’m not sure if hibernation might be to blame there.
Generally speaking, I would be looking at various Power Management Settings thingies wherever you can find them.
What are the right arguments to pass to journalctl to check my previous shutdown logs ?
There is no right or wrong. Choose the filter that suits your needs. man journalctl
For example, check logs from the previous boot:
journalctl -b
More filters in the manual.
After journalctl -p 3 -xb -1 to get errors and critical messages I got this:
mai 24 19:14:15 ttiagojm-DHFJ kernel: x86/cpu: SGX disabled by BIOS.
mai 24 19:14:17 ttiagojm-DHFJ kernel:
mai 24 19:14:20 ttiagojm-DHFJ kernel: i2c_hid_acpi i2c-ELAN1300:00: device returned incorrect report (2 vs 14 expected)
mai 24 19:14:29 ttiagojm-DHFJ bluetoothd[755]: src/plugin.c:plugin_init() Failed to init vcp plugin
mai 24 19:14:29 ttiagojm-DHFJ bluetoothd[755]: src/plugin.c:plugin_init() Failed to init mcp plugin
mai 24 19:14:29 ttiagojm-DHFJ bluetoothd[755]: src/plugin.c:plugin_init() Failed to init bap plugin
mai 24 19:14:42 ttiagojm-DHFJ gdm-password][1407]: gkr-pam: unable to locate daemon control file
mai 24 19:14:42 ttiagojm-DHFJ bluetoothd[755]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
mai 24 19:14:45 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 190 and the job result is failed.
mai 24 19:14:45 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 194 and the job result is failed.
mai 24 19:14:45 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 186 and the job result is failed.
mai 24 19:14:47 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 413 and the job result is failed.
mai 24 19:14:47 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 433 and the job result is failed.
mai 24 19:14:47 ttiagojm-DHFJ systemd[1421]: Failed to start Application launched by gnome-session-binary.
Meanwhile I tried to use linux-lts kernel but keeps happening. I realized that only happens when I keep the computer +6 hours On and I lock the screen multiple times.
Now I tried to uninstall nvidia drivers to see if that is a problem or not
Yeah I saw that and I play with the options but nothing changed
Just for funsies can you post your system info? Run these commands:
inxi -Fxxc0z | eos-sendlog
The eos-sendlog will give a pastebin url that you can post here for us to see this system info.
It looks like there’s a slightly newer BIOS version available than what you’re using, but not sure if that’s intentional. Not sure if this newer version could address the Power behavior of the USB bus/ports. https://www.asus.com/supportonly/x530ufo/helpdesk_bios/
Also, have you tried replicating the issue by using x11 instead of Wayland? You can easily switch at the login screen (in case you’re not aware).
Nope, I didn’t realize I have a newer BIOS version to update and I didn’t try to switch to xorg.
I’ll try both and see if something change
Well after some days the weird behavior disappear … I didn´t upgrade my BIOS but I changed to Xorg instead of wayland, uncommenting the following line in /etc/gdm/custom.conf:
WaylandEnable=false
And I removed nvidia drivers. One of them or both fixed my issue. Thanks @GUIn00b !
Solution here: Shutdown turn off screen but keyboard backlight keeps on EndeavourOS Gnome - #10 by GUIn00b
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.