https://bugs.kde.org/show_bug.cgi?id=504861
--- Comment #11 from Sanfod Rockowitz <rockow...@minsoft.com> --- I have made a fix to ddcutil 2.2.1-dev that resolves the issue, at least in the case that Martin documented, where PowerDevil doesn't restart when an "assertion" failed in libddcutil. The problem was that, for historical reasons, macro TRACED_ASSERT() used exit(1) instead of __failed_assert() to terminate library execution. This has been changed. Martin, thank you for the log that reported the assert failure. It changed the problem from "libddcutil fails for some reason and powerdevil doesn't restart" to "libddcutil fails for a specific reason and powerdevil doesn't restart". -- You are receiving this mail because: You are watching all bug changes.
