Open nishanthkarthik opened 1 year ago
That the plugin fails on first use, but works after reload, suggests that there are two different versions of the plugin. I'm not familiar with the plugin framework, but you might check if there are two copies of powerdevilupowerbackend.so on your system. The PowerDevil plugin is marginal, and most (all?) binary distributions do not build it with ddcutil enabled. arch is a source distribution, and it appears that normal practice is to build with all options enabled.
See this comment on an earlier issue thread from the person who implemented the PowerDevel/ddcutil code.
Alternatively, there might be an old copy of libddcutil.so that is being called first.
Note that code simplification in ddcutil 1.3 exposed a bug in the coding of the Nvidia proprietary driver. Release 1.4 backs out that simplification as a workaround. See the ddcutil release notes. However, it does not appear that this is the source of your problem.
Having said all that, ddcutil should not be going belly up because the API is misused. To capture libddcutil tracing, create file $HOME/.config/ddcutil/ddcutilrc with the following lines:
[libddcutil]
options: --thread-id --trace ddc --trace i2c --libddcutil-trace-file <YOUR_FILENAME_HERE>
To include debug symbols in libddcutil.so, call .configure as follows before make:
./configure CFLAGS="-ggdb3 -O0" CXXFLAGS="-ggdb3 -O0" LDFLAGS="-ggdb3"
It would also be useful to see if the problem still occurs when building from the current 1.4.1-release branch.
And of course, please submit any large output as an attachment of some sort rather than inline. Thank you.
This only happens the very first time I try to change the brightness on KDE. Once the powerdevil-ddcutil plugin crashes and reloads, it works as expected. I don't have the debug symbols at the moment.
Stacktrace
ddcutil.log