| Summary: | Inhibit button from system tray it doesn't work correctly | ||
|---|---|---|---|
| Product: | [Unmaintained] Powerdevil | Reporter: | Dmitry Nirox <nirox.linux.box> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | gaterix, kde, kde, kde, nate, nirox.linux.box |
| Priority: | NOR | Keywords: | regression |
| Version First Reported In: | 5.22.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=438698 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dmitry Nirox
2021-06-15 17:22:02 UTC
Works for me with a ThinkPad X1 Yoga (gen 4): with the checkbox unchecked, the screen locks/suspends at the normal schedule, and with the checkbox checked, it does not. Are there any app-specific inhibitions? You're saying that this issue was happening to you in the past with a different laptop? Were you using Plasma 5.22 on that laptop, or was it an earlier version? Thank you for checking it out. Both laptops are running under 5.22 now (Kubuntu 21.04 + KDE backports) . No specific programs or restrictions are used. The only point I do not install TLP utilities. https://linrunner.de/tlp/ I do not install it because in the case of P14s (AMD), the LAN adapter stops working correctly. Yes, the same problem was on earlier versions. I have to use Activities with special nutrition conditions when I need the laptop to stay awake. This is the wrong way, I know, but otherwise you have to log out of the session every time. I tried this feature even on the system immediately after installation, the same thing. I don't understand where my mistake can be. Still simple, click and it works. And I'm sorry that there are no technical details, although I have been using Linux for more than 10 years, but as a user, not a developer. Thanks for the info. We have another report in Bug 438698 from someone with the same chipset, so it's possible that it's a bug particular to that hardware. It will need investigation with someone more familiar with the power management stuff that I am (which is to say, at all). *** Bug 438843 has been marked as a duplicate of this bug. *** Two reports of this now; marking as confirmed and VHI regression even though I cannot personally reproduce it, because clearly other people can. :( I also cannot reproduce. Please confirm no other processes are running that could be inhibiting screenlocking themselves. After that please can you set the screensaver timeout and record 1 minute of `dbus-monitor --pcap` Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |