Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 892846 - >=sys-apps/systemd-252.4 breaks hibernation
Summary: >=sys-apps/systemd-252.4 breaks hibernation
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Normal normal
Assignee: Gentoo systemd Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-01 17:16 UTC by Axel Gerber
Modified: 2023-07-23 20:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info is enclosed as .txt file (emerge-info.txt,7.10 KB, text/plain)
2023-02-01 17:16 UTC, Axel Gerber
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Gerber 2023-02-01 17:16:21 UTC
Created attachment 849636 [details]
emerge --info is enclosed as .txt file

I use a Lenovo T450s with plain gentoo (emerge --info attached)

- TLP is and was installed for power management from overlay. Never had an issue
- Hibernation was working well since April 2020
- Hibernation worked well last time on 14th Jan 2023 (acc. to my logs)
- On Jan. 15th there was an update of systemd-252.4, Jan 28th systemd-252.4-r1

Since Version 252.4 hibernation still works when triggered manually (diff. command line or via sddm or kde). 

However, the timeout which is set in /etc/systemd/sleep.conf _does not work_ anymore. Means the machine goes to S3 and stay there as long battery lasts.
- no any good hint in the logs or journalctl. Just as there would be no /etc/systemd/sleep.conf

Downgrade to systemd-251.8 makes the hibernation work well again acc. to the timeout.

-------------------
Sidenote: I donno where to address this well:
I am really unhappy recently gentoo-team removes older versions from repo too fast. If 251.x would be still in repo, I could do a roll back in minutes. As I am not a pro, it cost me 3h to do the roll back. (Admitted that this is necessary for incompatibilities or breakages or blockages, but that was not the case in the four (4!) recent cases I encountered. I would appreciate this habit gets changed.
Comment 1 Mike Gilbert gentoo-dev 2023-02-01 20:05:57 UTC
(In reply to Axel Gerber from comment #0)
> I am really unhappy recently gentoo-team removes older versions from repo
> too fast.

I can make a note to keep old versions around for a couple of weeks after a new version is marked stable, assuming there are no security bugs associated with the old version.
Comment 2 Mike Gilbert gentoo-dev 2023-02-01 20:08:30 UTC
I would suggest looking for a relevant issue upstream, or creating a new one.

https://github.com/systemd/systemd/issues
Comment 3 Axel Gerber 2023-02-01 20:21:21 UTC
(In reply to Mike Gilbert from comment #2)
> I would suggest looking for a relevant issue upstream, or creating a new one.
> 
> https://github.com/systemd/systemd/issues

done!
https://github.com/systemd/systemd/issues/26296
Comment 4 Axel Gerber 2023-02-01 20:23:10 UTC
(In reply to Mike Gilbert from comment #1)
> (In reply to Axel Gerber from comment #0)
> > I am really unhappy recently gentoo-team removes older versions from repo
> > too fast.
> 
> I can make a note to keep old versions around for a couple of weeks after a
> new version is marked stable, assuming there are no security bugs associated
> with the old version.

Vacation + "time to notice" (not short for a 'second device') = pls reasonably 'long' :-)

Thank you!
Comment 5 Mike Gilbert gentoo-dev 2023-07-22 20:55:30 UTC
Should be fixed in recent systemd versions.
Comment 6 Axel Gerber 2023-07-23 20:04:20 UTC
I can confirm, in the current systemd-253.3 it is fixed...