https://bugs.kde.org/show_bug.cgi?id=523404
Ariane <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #12 from Ariane <[email protected]> --- (In reply to Nate Graham from comment #11) > I'm afraid you're going to need to figure out what thing is inappropriately > blocking sleep yourself. It sounds like you have a very complex setup with a > lot of devices; maybe try unplugging all of them and re-plugging them one at > a time to see if one specific one causes it. Or turn off KDE Connect > entirely for a bit and see if the issue stops happening. > > See also https://community.kde.org/Troubleshooting, which may be helpful. Hi! I unpaired KDE Connect a few days ago, but the issue kept happening. I started opening my terminal and using `journalctl --follow` as soon as I turned my PC on, and opening the Power & Battery applet as soon as I was leaving the PC idle. Sadly, the Power & Battery applet was always closed when I came back to the PC, so I didn't get any info that way. Then, today, the issue happened and I had an idea. I stepped over to the PC, and unplugged one of the two USB devices (actually hubs) plugged into it. Then I left without interacting with the PC. I waited a while (more than 10 minutes) and saw that the PC's screen was still not off. So I yanked the other USB hub, again without interacting, leaving my PC with nothing plugged in but: - One DP monitor - One HDMI TV - An Ethernet cable leading to my router - The power cord When I came by again more than 10 minutes later, the screen was still on. I plugged my devices back in (because otherwise I can't do anything; it's a tower, not a laptop), and hit Ctrl-C in the Terminal, hit "Save output as..." intent on sharing the full logs here. But actually there's only a few minutes of stuff in the logs. So I don't think there's much useful info in there... I also checked Power & Battery, but as usual, there was nothing there. I'll share what logs I have from that command anyway though. I also saved a backup of my /var/log folder too. I have no idea whether it contains useful info, but don't hesitate to ask me for something in there. So anyway, I'm not sure I'm providing anything useful when it comes to narrowing down the issue, but what this experiment has told us for sure is: - The issue is not caused by my phone sending over something through KDE Connect - The issue is not caused by any of my USB devices, since it persisted when 0 USB devices were connected to the PC. What should I do next? -- You are receiving this mail because: You are watching all bug changes.
