https://bugs.kde.org/show_bug.cgi?id=481793
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Jakob Petsovits <jpe...@petsovits.com> ---
Can confirm. Plasma's use of ddcutil hasn't really changed much in 6.0 vs.
5.27, I would presume that this is due to changes in (lib)ddcutil itself to
avoid two different apps getting in each others' way. For Plasma 6.1, we're
adding the ability to keep track of monitors being added or removed, i.e.
hotplugging, so the need to keep ddcutil running within PowerDevil will only
increase.
I'm not sure if ddcutil is considering plans to allow multiple programs to
access it simultaneously. From the Plasma point of view, I don't see an easy
way of resolving this conflict.
What you can do in Plasma 6.0 is to set an environment variable
POWERDEVIL_NO_DDCUTIL=1 which will disable the use of ddcutil within
powerdevil. On a system with systemd, you can add a snippet to the
plasma-powerdevil service:
$ systemctl edit --user plasma-powerdevil.service
(opens an editor, modify as follows:)
### Editing
/home/kpetso/.config/systemd/user/plasma-powerdevil.service.d/override.conf
### Anything between here and the comment below will become the contents of the
drop-in file
[Service]
Environment="POWERDEVIL_NO_DDCUTIL=1"
### Edits below this comment will be discarded
and then restart PowerDevil with `systemctl restart --user
plasma-powerdevil.service`. Obviously that also means you won't be able to
configure brightness with it that way. But you'll be able to use the ddcutil
CLI instead. Sorry that this is the best I can do at this time.
--
You are receiving this mail because:
You are watching all bug changes.
