SUMMARY I left my computer untouched for a while, so the screen locked and turned off as expected. I shook the mouse and unlocked the screen and I went to Power and Battery because I wanted to manually block screen locking and sleep. To my surprise, I found out it said (and says right now) that "Google Chrome is currently blocking sleep and screen locking (Download in progress)" (BTW I had to painfully write all that text by hand as there is no way to select and copy it). Evidently that is false, as proven by the fact that I just had to unlock the screen a few minutes ago. Also, there is no download in progress, that's completely false (I did download some files at some point but that was many hours ago). I don't think this is 418433 (in which it would be true that Chrome is blocking sleep, but not screen locking) because there's no reason for that either, and again, if the reason was "download in progress", there's no download in progress. STEPS TO REPRODUCE I don't know of any reproducible way to trigger this. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.6.119-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 16 GiB of RAM (15.3 GiB usable) Graphics Processor: Intel® Iris® Xe Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA System Version: 1.0
LOL I have now closed Google Chrome (and checked that no Chrome process is running), and the Power and Battery widget STILL says that Google Chrome is blocking screen locking and sleep. It is completely ridiculous that it's even possible for an application that is not running to be reported as blocking sleep.
Interesting, for me chrome did not inhibit at all while downloading. In your case, I believe there may have been a stuck chrome process in the background. Likely a bug with chrome itself. Operating System: KDE Linux 2026-02-01 KDE Plasma Version: 6.6.80 KDE Frameworks Version: 6.23.0 Qt Version: 6.10.2 Kernel Version: 6.18.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600
> In your case, I believe there may have been a stuck chrome process in the background. No, as I said I checked. Unless the process didn't have "chrome" in its name (I checked with "ps aux |grep chrome").
(In reply to php4fan from comment #3) > > In your case, I believe there may have been a stuck chrome process in the background. > > No, as I said I checked. Unless the process didn't have "chrome" in its name > (I checked with "ps aux |grep chrome"). Hm, do you use Chrome flatpak? Could be the flatpak process itself that got frozen.
> Hm, do you use Chrome flatpak? No. BTW I've seen this many times, always with Chrome as far as I remember, although I'm not sure if it always said "Download in progress" or not. I'm not sure which one of these two things is happening: A) nothing is actually blocking anything, the system can lock screen and go to sleep, but the widget has somehow missed that information, or B) only sleep is actually being prevented, and because of 418433 the widget reports that both sleep and screen lock are being prevented. (if I remember to pay attention I'll be able to tell tomorrow) IF it's B (and that's a big 'if'), then the next question is why sleep is being prevented for no reason. As long as Chrome is still running, that could be Chrome's fault, that asked to block sleep and then "forgot" to unblock it; but if that was the case, it should go away once I close Chrome, and it doesn't. So it's either entirely a bug in KDE, or a bug in Chrome (forgetting to unblock) _and_ one in KDE (not unblocking when the process that requested the block is no longer running). And of course if it's A then it's a bug in KDE because the information given by the widget does not reflect reality.