[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-08 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 flan_suse changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-03 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #8 from flan_suse --- This might be upower after all. I'll keep on eye on things, and see what happens with upstream upower. (However, I did try with an earlier version of upower, and the same issue persisted.)

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-02 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #7 from flan_suse --- (In reply to flan_suse from comment #6) > Notice there's a 3-minute gap in the log? To emphasize this point, for all intents and purposes the system *did* in fact "suspend". No activity logged for 3 minutes, until I

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #6 from flan_suse --- Created attachment 147231 --> https://bugs.kde.org/attachment.cgi?id=147231=edit journalctl when suspending with KDE 5.24 Notice there's a 3-minute gap in the log? That's how long I waited while the system was

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #5 from flan_suse --- Keep in mind when this bug occurs, my fans STOP. Monitor shut off (no signal). However, for some reason my CPU is heating up rapidly, since it's somehow still running, but without the cooling of the fans. I can attach

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #4 from flan_suse --- Created attachment 147217 --> https://bugs.kde.org/attachment.cgi?id=147217=edit Output of "systemd-inhibit --list" when KDE and SDDM are *NOT* running. Output of "systemd-inhibit --list" when KDE and SDDM are *NOT*

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #3 from flan_suse --- Created attachment 147216 --> https://bugs.kde.org/attachment.cgi?id=147216=edit Output of "systemd-inhibit --list" when KDE and SDDM are running. Output of "systemd-inhibit --list" when KDE and SDDM are running.

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 --- Comment #2 from flan_suse --- (In reply to David Edmundson from comment #1) > Please test with "systemctl suspend" > > If that behaves the same, the issue isn't our side. > > systemd-inhibit --list might also be useful It gets more interesting.

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=450980 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[plasmashell] [Bug 450980] KDE 5.24 breaks suspend to RAM (really badly); reverting to 5.23 resolves it

2022-03-01 Thread flan_suse
https://bugs.kde.org/show_bug.cgi?id=450980 flan_suse changed: What|Removed |Added Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general