https://bugs.kde.org/show_bug.cgi?id=476375
--- Comment #60 from Jakob Petsovits <jpe...@petsovits.com> --- Alright folks, the commit from Comment #59 is going to be in Plasma 6 RC1, a.k.a. version 5.92.0 and above. What this means is that you can now create a file called $HOME/.config/ddcutil/ddcutilrc. If present, both the PowerDevil daemon and ddcutil will read and interpret it. The contents could look e.g. like this: [global] ; Combined with all other options strings options : --trace-to-syslog-only --trcfunc ddc_write_read_with_retry --trcfunc ddc_write_read There is a slightly more detailed documentation page for this file at https://www.ddcutil.com/config_file/ and a listing of the numerous ddcutil options at https://www.ddcutil.com/options_main/ - go nuts if you're into debugging. Any ddcutil tracing output will show up in journalctl, under org_kde_powerdevil. I don't know enough about ddcutil to tell what a good set of options would be to debug this particular use case, maybe the above are a good start or maybe they're unreadable noise. Not sure, we'll have to figure it out as we go along. You can also try specifying some of the options that change how ddcutil behaves. If you find an options that magically fixes things for you, that would be a *very* solid data point. But even without that, we should now have some tools on hand to communicate effectively with the ddcutil maintainer on his GitHub page: https://github.com/rockowitz/ddcutil/issues/ Another thing you can do for better reporting is to make PowerDevil's own logging statements show up in journalctl. Tell systemd to give you an editor by calling: systemctl edit --user plasma-powerdevil.service Then add something like this to the empty space "between here and the comment below": [Service] Environment="QT_LOGGING_RULES=*.debug=true;qt.*.debug=false" This will tell us approximately how far you made it into PowerDevil's DDC code. You can already do this with previously released versions of PowerDevil, too. To actually see the output without having to log out and back in, restart just the PowerDevil daemon with: systemctl restart --user plasma-powerdevil.service When posting output, please use pastebin sites such as https://paste.kde.org/, https://gist.github.com/ or https://pastebin.com/ and link to those pastes. It's already a very long bug, let's try to keep it relatively tidy. Thanks everyone for helping to get this nailed down! -- You are receiving this mail because: You are watching all bug changes.
