Summary: | When an app inhibits sleep and screen locking the user is not informed of that app, leading to a silent fail | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Répási Dávid <hu.repasidavid> |
Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | nate |
Priority: | NOR | ||
Version First Reported In: | 6.3.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Répási Dávid
2025-04-02 15:45:51 UTC
When calling 'systemctl suspend' in the terminal, it shows what app and why it's blocking That's not quite how this works; when an app blocks sleep and screen locking, it only blocks *automatic* sleep and screen locking. You should be able to manually initiate these yourself. I gather that's not happening? If you prevent the apps from blocking sleep and screen locking using the "Unblock" button on the Power and Battery widget, are you able to manually initiate sleep or screen locking? Or does that continue to fail? So, I tried with other torrent clients as well, but this only happens with qbittorrent for me. Options enabled: Preferences -> Behaviour -> Power Management -> both options When using the 'Unblock' feature - either option, nothing happens, just the silent fail. Only when QBitTorrent blocks sleep, and not for any other apps? That's very strange. FWIW, I can't reproduce the issue; when I install QbitTorrent, use those settings, and start a torrent, I can manually put the system to sleep as expected. Can you reproduce this issue in a new clean user account? It works fine on a different machine with a clean install. Thanks. How about in a new clean user account on the same machine? Works fine on a newly created user account as well. Could be some update borked a config file in a past update. Could be indeed. If you could try to figure out what configuration is causing the issue, that would be amazing. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |