rockowitz

You hit a bug in the recently added configuration file code. As a work-around, create a dummy configuration file: `$ touch $HOME/.config/ddcutil/ddcutilrc`

There are 2 separate problems going on. The DDC "Null Response" is a well formed DDC response from the monitor. It's a bit of a catch-all, but basically it's the...

Ben, I should have caught this before, but looking at the **environment** output again I see that you're running kernel 4.18. Support for DDC on monitors connected to docking stations...

Detecting display changes is just the first step. Data structures need to be updated, and these changes need to be made visible in the API. My plan is to use...

@FedeDP Hi Federico, I believe I've plugged the memory leaks you've found. The changes are in the current development branch, 1.2.1-dev. These are the first changes in upcoming release 1.2.1...

@FedeDP After addressing your latest leak report, I spent much of yesterday on the hunt for memory leaks. Most of what's left is in initialization code. Let me know how...

@pjaitken I have, as they say, been admiring your problem, and trying to think of useful things to suggest. PBP is so beyond what was considered when MCCS was defined....

@bugrasan Most of my reply to @pjaitken is for you as well. The one thing I would add is that the **watch** command is problematic. The version in branch 1.0.0-dev...

I'm not sure what to make of the feature x20 and x30 discrepancies. These features are in the Geometry section of the MCCS spec, which contains features like pincushion that...

Re the x52 deviations, I would expect the value of feature x52 to vary based on the monitor's state. That the value of x52 is x00 for **scan** suggests that...