You are not logged in.
SOLVED:
It's a bug of newer kernels. Going back to linux-lts-6.6.27-1-x86_64.pkg.tar.zst solve this problem.
____
Hello,
Sorry for the vague title. My computer doesn't shut down properly after long periods of work. The screen turns off, but my keyboard remains lit. I have to force shutdown the computer by long-pressing the power button.
It seems to be related to my work in VSCode. When i3 shuts down, I briefly see many log messages. Unfortunately, these log messages are nowhere to be found, not even under '/var/log'. The short log output displays some file paths of the files I was working with.
I've tried to capture the messages with my smartphone camera, but the image is blurry, and I can't reproduce the errors that quickly.
Could you please tell me where these error messages are landing?
Thanks!
Last edited by Lax Lexis (2024-05-01 08:22:24)
Offline
"sudo journalctl -b -1" but if the error (the image text isn't readable) occurs after the journal was synced: nowhere.
You can makeshift a triod by jammign your pohne between two books -\_ what might lead to a less blurry image.
Offline
I edit the image! Now it is readable:
It seems that there is a problem with cups, among other things. That's correct. I use chromium a lot, especially its print feature. Apparently, something isn't right there. Maybe it's because my cups.service isn't enabled. However, that shouldn't lead to such errors.
Any suggestions?
Offline
This is all from during until terminating the i3 session and stuff that would typically go into .xsession-errors and not relevant to the shutdown freeze.
The photo looks like there're residuals of the x11 session on the top and the console messages on the bottom and I guess you're looking at some frozen framebuffer?
Just post the system journal of the previous boot.
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
Offline
Maybe something goes wrong with paperwork-gtk. :-/
Last edited by Lax Lexis (2024-04-28 10:11:35)
Offline
It crashes but that doesn't impede the shutdown - the system actually does
…
Apr 28 11:43:47 thinkpadz13gen2 systemd[1]: Reached target System Power Off.
Apr 28 11:43:47 thinkpadz13gen2 systemd[1]: Shutting down.
Apr 28 11:43:47 thinkpadz13gen2 systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 28 11:43:47 thinkpadz13gen2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 28 11:43:47 thinkpadz13gen2 systemd-journald[336]: Received SIGTERM from PID 1 (systemd-shutdow).
Apr 28 11:43:47 thinkpadz13gen2 systemd-journald[336]: Journal stopped
https://gitlab.archlinux.org/archlinux/ … /issues/45
Does it happen w/ 6.8.6 or the LTS kernel?
Offline
https://gitlab.archlinux.org/archlinux/ … /issues/45
Does it happen w/ 6.8.6 or the LTS kernel?
Wow, you're a genius. I have exactly the same bug. I wouldn't have thought it was related to sleep mode. So, it's not about my computer work, but simply that I closed the notebook after a long work session. But yes, I can quickly reproduce the bug. Unfortunately, I'm already on the LTS Kernel: 6.6.29-1-lts and the bug still exists. I'll try later with Current and Mainline.
Last edited by Lax Lexis (2024-04-29 09:04:28)
Offline
Not a genius, just around.
https://bbs.archlinux.org/viewtopic.php?id=295199&p=3
Teh offending patch was unfortunately backported to 6.6.29 or 28 the older LTS kernels would also still work.
Offline
Ok, thanks. Bug still exists in 6.8.7 and since 6.8.8 the suspend is totally broken (for Thinkpad Z13/Z16): A wake up ends with freeze ... I will wait.
Offline
If you get tired of waiting you can interim downgrade to an unaffected kernel, https://wiki.archlinux.org/title/Arch_Linux_Archive
Offline
I've already done that, but without the archive. I rarely clear my pacman cache, so I even found linux-lts-6.6.22-1-x86_64.pkg.tar.zst. Currently I am back to linux-lts-6.6.27-1-x86_64.pkg.tar.zst and everything works fine.
Offline