https://bugs.kde.org/show_bug.cgi?id=515395
--- Comment #5 from [email protected] --- > 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. -- You are receiving this mail because: You are watching all bug changes.
