https://bugs.kde.org/show_bug.cgi?id=476375
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jpe...@petsovits.com
--- Comment #58 from Jakob Petsovits <jpe...@petsovits.com> ---
The stacktrace by Markus in comment 39 is a good one, but it's hidden deep in
the first ddcutil function that powerdevil calls. Seems unlikely that it would
have been KDE's fault at that point. The other two or so stacktraces were not
useful.
I had a little bit of a look at what's new in ddcutil 2.0.0; among other
things, it introduces an optional initialization function. Calling this (or
not) shouldn't make a difference in how ddcutil behaves by default, but it does
allow any user to turn on copious amounts of trace logs that should help with
producing more useful information for us or the ddcutil maintainer. These will
show up in your journalctl logs under the 'org_kde_powerdevil' name once the
above merge request goes in.
You'll have to wait for the next Plasma 6 release candidate after that in order
to use this for debugging, or build Plasma from scratch. Frankly, KDE devs
won't be able to do overly much with ddcutil traces and we'll probably have to
ask for help on the ddcutil issue tracker. But if the crash is really in
ddcutil's court, being able to log traces and test non-default behavior with
runtime options is going to help us iterate faster.
--
You are receiving this mail because:
You are watching all bug changes.
