rockowitz

MST connections can behave problematically. It's often the case that he same MST connected monitor will appear on two different /dev/I2c buses. What I've never seen is the card-connector identifiers...

Based on our earlier exchanges, I added recognizing EDID values encoded in Base64 to the [enhancement list](https://github.com/rockowitz/ddcutil/discussions/525). If you think a shorter representation, that isn't guaranteed to be unique, would...

The one thing that's peculiar in your interrogate output is that **ddcutil** learns of the laptop display on card1-dDP-1 and /dev/i2c-4 by querying /sys. However, trying to read the EDID...

I'm afraid I don't see what to fix here. You're running CachyOS on an old IdeaPad; I'd need a similar system to diagnose further. I can say that I've run...

I believe what you're saying is that your application uses libddcutil, and you would like it to notify your client program if brightness is changed by command line ddcutil. This...

What version of ddcutil does this occur with? At first glance it looks like a bug introduced in 2.2.0 that was fixed in 2.2.1. See issue #528.

It should be in the system log. **journalctl -t org_kde_powerdevil**, look for line containing "Initializing libddcutil".

Also, can you build from branch 2.2.2-dev and confirm the problem exists with that branch?

Also if possible: - output of **journalctl -t org_kde_powerdevil**, starting with the "Initializing libddcutil" line, that show the error - instructions on how to reproduce the error

Can you ask users to submit the output of **journalctl -t org_kde_powerdevil** described above? Github users can submit it (as an attachment) to this issue; anyone can send it to...