Clight freezes part of screen

[jghauser]

When I run clight -c the bottom ~2/3 of my screen freeze (a sharp horizontal line separates the two areas). That is, the bottom part continues to display what has been there before and does not update anymore. The only way to solve this is a reboot (as far as I know). I'm on Arch Linux, using X and i3, everything fully updated.

Here's the output of clight -c --verbose:

% clight -c --verbose
Config file /home/julian/.config/clight.conf not found.
Signal module started.
Bus module started.
UserBus module being started as submodule of Bus...
UserBus module disabled.
Disabling module Inhibit as its hard dep UserBus was disabled...
Inhibit module disabled.
Trying to start Dimmer module as its Inhibit soft dep was disabled...
Inhibit module destroyed.
UserBus module destroyed.
Xorg module disabled.
Disabling module Gamma as its hard dep Xorg was disabled...
Gamma module disabled.
Trying to start Brightness module as its Gamma soft dep was disabled...
Location module disabled.
Location module destroyed.
Gamma module destroyed.
Disabling module Dimmer as its hard dep Xorg was disabled...
Dimmer module disabled.
Dimmer module destroyed.
Disabling module Dpms as its hard dep Xorg was disabled...
Dpms module disabled.
Dpms module destroyed.
Xorg module destroyed.
Clightd found, version: 2.2.
Clightd module started.
Trying to start Brightness module as its Clightd dependency was loaded...
Trying to start Brightness module as its Bus dependency was loaded...
Trying to start Upower module as its Bus dependency was loaded...
Upower module disabled.
Trying to start Brightness module as its Upower soft dep was disabled...
AC curve: y = -0.024825 + 0.191641x + -0.008928x^2
BATT curve: y = -0.010629 + 0.153844x + -0.007284x^2
Set timeout of 0s 1ns on fd 6.
Brightness module started.
Upower module destroyed.
Average frames brightness: 0.053657.
New brightness pct value: 0.075434
Brightness module destroyed.
Clightd module destroyed.
Bus module destroyed.
Signal module destroyed.

Any idea what could be up here? Thanks a lot for developing this very promising tool!

[Dr-Ongo]

Okay, after a reboot and running the patched clightd with i2c-dev loaded I got the same output as before, but my screen did freeze.

[FedeDP]

Great! Thanks, we now know that is the function in ddcutil that is causing the issue!

[FedeDP]

Can I ask you to join me and @rockowitz on related ddcutil issue?

Btw can you try, with i2c-dev module loaded, to issue this commands and let us know (on the aforementioned ddcutil issue) which one triggers the freeze (if any)? ddcutil detect
ddcutil detect --verbose
ddcutil environment
ddcutil environment --verbose

Thank you very much for all the time you're spending helping us debug this issue! @Dr-Ongo @jghauser

[FedeDP]

As it is now certain that this is not a Clight issue, i'm going to close this.

Let me thank you both (@jghauser @Dr-Ongo) once more for the great help you provided (and are still providing!) to me and to ddcutil main developer. Let's hope to get this issue fixed in next ddcutil release!

[rockowitz]

I'd like to extend my thanks as well to @jghauser and especially @Dr-Ongo, who has diligently tested ddcutil builds as we've diagnosed this problem.

Sanford

On 10/12/2018 10:23 AM, Federico wrote:

As it is now certain that this is not a Clight issue, i'm going to close this.

Let me thank you both (@jghauser https://github.com/jghauser @Dr-Ongo https://github.com/Dr-Ongo) once more for the great help you provided (and are still providing!) to me and to ddcutil main developer. Let's hope to get this issue fixed in next ddcutil release!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FedeDP/Clight/issues/35#issuecomment-429343281, or mute the thread https://github.com/notifications/unsubscribe-auth/ANhsbjkGjP5pJ395ne6we5ANkQaQHpsyks5ukKXLgaJpZM4WOAEz.