rockowitz
rockowitz
What's the output of **ddcutil det -v --f2**?
I've seen this behaviour. On my deskstop system, I've found that if a monitor is removed the edid can still be there, and if a different monitor is connected the...
As a first step, I've added some asserts, which along with valgrind should indicate where the g_path_get_basename() calls are failing and suggest where to look further. As you can see...
Yes, please test with the latest code. Until I can reliably recreate the problem here, all I can do is stare at the code. Thanks.
Doing too many things today .. I just pushed the changes.
So if you run the exact same steps that produced ddcutil-det-f2-problem.log, you get the same output as before with the GLib-CRITICAL msgs re g_path_get_basename, but no asserts in libddcutil. Is...
The assert failure in drm_common.c has been fixed. I came across a clue this afternoon as to why a test case for for the missing DRM information is elusive. See...
It's a proof of concept hack, but try the following in your failure scenario: - plug the monitor in - verify that status=disconnected and edid has no value - execute...
A fix for the segfault in get_enum_value_name() has been pushed to branch 2.1.5-dev
What happens now if you run through your test sequence with **ddcutil detect -v --enable-try-get-edid-from-sysfs --f15** What is the output of **cat /sys/class/drm/card0-DP-2/edid | parse-edid** before and after the above...