https://bugs.kde.org/show_bug.cgi?id=510992
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #51 from [email protected] --- I thought I should add that the same bug(s) (or at least bugs with the same solution of making wakeupsourcehelper not executable) can have worse consequences: on my lenovo x1 yoga gen 8, suspend invoked by powerdevil almost always seemed to succeed, but then led to a hard lock-up on resume, with the log file showing "PM: Some devices failed to suspend, or early wake event detected", showing that problems already occurred during the suspend. For discussion of similar problems, see https://discuss.kde.org/t/system-hanging-on-suspend/42672/19. In my particular case, using the suggestion above (https://bugs.kde.org/show_bug.cgi?id=510992#c26) to increase the level of information in the log, it looks like the actual culprit leading to the wake event is thunderbolt, though I'm not completely sure (nor clear on how best to investigate). For reference, the problems only started when upgrading powerdevil from 6.3.6 to 6.5.3 last December, consistent with what was found here. Anyway, I'm happy again being able to close the lid to suspend (rather than have to switch to a terminal) and hopefully this comment will at least make it easier for others to find a solution via googling (I was led to the solution and above link via Google's AI initially, having spent more time than I care to admit last year doing searches). -- You are receiving this mail because: You are watching all bug changes.
