https://bugs.kde.org/show_bug.cgi?id=470913
Bug ID: 470913
Summary: With multiple power Battery & Brightness widgets,
"manually block" state isn't synchronized/
Classification: Applications
Product: systemsettings
Version: 5.27.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_powerdevil
Assignee: plasma-b...@kde.org
Reporter: o...@geek.co.il
CC: k...@privat.broulik.de, natalie_clar...@yahoo.de
Target Milestone: ---
SUMMARY
I have setup - in addition to the Battery & Brightness popup widget in the
system tray - more Battery & Brightness widgets on the desktops in each of the
activities I use - so it is always very accessible. When I change any of the
sliders on the widget - that change is immediately reflected in all the other
copies of Battery & Brightness. But when I toggle the "Manually block sleep and
screen locking" checkbox - it is not reflected in any other copy, i.e. there is
one copy of Battery & Brightness that shows that locking is inhibited, but all
other copies don't show anything, not even the "X is inhibiting sleep & screen
locking" message that appears when something is inhibiting sleep.
The problem with that is that I use manual inhibiting quite a lot, but often
forget in which activity I did that, so when I look at the other widget and see
it isn't blocked, I feel I can walk away from my computer and when I come back
I see our malicious CISO had change my wallpaper to an annoying message about
locking my computer!
STEPS TO REPRODUCE
1. Add a Battry & Brightness widget to your background.
2. Make sure the CISO has an image with red text on black background saying
something like "You should always lock your computer!".
3. Open the Battery & Brightness system tray widget and check "Manually block
sleep and screen locking".
4. Work on something for a while.
5. Get up and stretch, look at your Battery & Brightness widget on the desktop
and see that its "Manually block sleep" checkbox is off. Conclude that its OK
to go get that espresso you'd been promising yourself for the last couple of
hours.
OBSERVED RESULT
You come back to find your screen unlocked, your wallpaper is now an ugly red &
black nightmare, and the CISO evilly sniggering in his corner office.
EXPECTED RESULT
You would notice that your system is inhibited, so you manually lock the screen
before leaving to get that espresso.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.9
Kernel Version: 6.2.0-20-generic (64-bit)
Graphics Platform: offscreen
Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
ADDITIONAL INFORMATION
I've known people whose CISO does `rm -rf $HOME` and then feign ignorance when
they exclaim that the company's backup software had been misbehaving the last
couple of weeks and there are multiple open IT tickets about that. Luckily, I'm
not in that situation 😅.
--
You are receiving this mail because:
You are watching all bug changes.
