https://bugs.kde.org/show_bug.cgi?id=491480
fanzhuyi...@gmail.com changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=491480
--- Comment #8 from Arek Guzinski ---
After doing a clean reinstall of the newly rebased Neon, this is working fine
again.
But I'm not convinced the problem is really gone until it has been working for
at least a year..
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=491480
--- Comment #7 from Arek Guzinski ---
Small update:
* I did not downgrade systemd because of the dependency problems this would
cause.
* I searched the relevant systemd bugtrackers (github & ubuntu package) for
this problem - found nothing.
--
You ar
https://bugs.kde.org/show_bug.cgi?id=491480
Tapio Metsälä changed:
What|Removed |Added
CC||tapio.mets...@elisanet.fi
--- Comment #6 from T
https://bugs.kde.org/show_bug.cgi?id=491480
--- Comment #5 from Arek Guzinski ---
Sounds reasonable. But what could it be?
/etc/systemd/sleep.conf has not been touched since 2022.
/etc/systemd/system/sleep.target.wants and it's contents have a mtime in 2021.
I don't think, I manually changed a
https://bugs.kde.org/show_bug.cgi?id=491480
--- Comment #4 from fanzhuyi...@gmail.com ---
Given that echo mem > /sys/power/state works but systemctl suspend does not, my
guess would be that maybe some systemd sleep hook is blocking sleep.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=491480
fanzhuyi...@gmail.com changed:
What|Removed |Added
CC||carlosdema...@gmail.com,
