https://bugs.kde.org/show_bug.cgi?id=517571
Sanfod Rockowitz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Sanfod Rockowitz <[email protected]> --- I've pushed a fix to github ddcutil branch 2.2.7-dev. The line number in the trace does not map to either of the assert() statements in function dw_redetect_displays(), and without journalctl output I can't be absolutely certain of what's going on, but it looks like the proximate cause is that ddca_redetect_displays() was called when display detection was not running. I'm pretty sure that journalctl would show that function ddca_start_watch_displays() failed for some reason, or that it wasn't ever called. I've replaced the asserts() with code that writes to the system log. If watching for display changes was not active when ddca_redetect_display s() was called, it does not attempt to restart it when display redetection is complete. I see that the DDCutilPrdvateSingleton constructor does not check the return code from ddca_start_watch_displays(), You probably want to check it to know if display change detection is actually running, though that is not a factor here. Finally, ddcutil issue https://github.com/rockowitz/ddcutil/issues/587, Assert failure in ddc_packet_io.c:372 #587, is unrelated to this bug. It occurred because of a race condition and should be fixed in ddcutil 2.2.6. -- You are receiving this mail because: You are watching all bug changes.
