https://bugs.kde.org/show_bug.cgi?id=350258
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=350258
--- Comment #7 from Kai Uwe Broulik ---
That's not a solution. It has to be something PowerDevil can do, like it tells
Logind on DBus not to auto-suspend because we're handling that. I'll ask on the
systemd mailing list then ...
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=350258
--- Comment #6 from Mark ---
I really hate the annoying behavior of the systemd developers to introduce
services that you can't simply shut down! There really is something wrong in
their logic.
But yes, it can be disabled.
systemctl mask systemd-backli
https://bugs.kde.org/show_bug.cgi?id=350258
--- Comment #5 from Kai Uwe Broulik ---
> Anyhow, when systemd remembers the brightness and restores it, Why not just
> show a message in PowerDevil that SystemD is managing brightness by default
> thus managing through PowerDevil is disabled.
A user
https://bugs.kde.org/show_bug.cgi?id=350258
Mark changed:
What|Removed |Added
CC||mark...@gmail.com
--- Comment #4 from Mark ---
(In repl
https://bugs.kde.org/show_bug.cgi?id=350258
--- Comment #3 from Kai Uwe Broulik ---
That doesn't stop PowerDevil from overriding it on login :)
Also, I hate that systemd messes with brighrness. Yet another service that
thinks it knows better. Any way to inhibit that?
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=350258
Alex Fiestas changed:
What|Removed |Added
CC||afies...@kde.org
--- Comment #2 from Alex Fiesta
https://bugs.kde.org/show_bug.cgi?id=350258
Kai Uwe Broulik changed:
What|Removed |Added
Component|general |general
Assignee|plasma-b...@kde.or
