Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] ddcutil flooding the logs #379

Open
saipavanc opened this issue Jan 14, 2025 · 0 comments
Open

[BUG] ddcutil flooding the logs #379

saipavanc opened this issue Jan 14, 2025 · 0 comments

Comments

@saipavanc
Copy link
Contributor

Describe the bug
When I am using the brightness setting on my panel, I am able to change the brightness of my scree, albeit a little buggy. But, I see that my logs are getting flooded with the following message:

Jan 14 10:45:12 sai-precision3440 ddcutil[7337]: busno=5, All features that should not exist detected. Monitor does not indicate unsupported
Jan 14 10:45:12 sai-precision3440 ddcutil[7337]: busno=6, sleep-multiplier =  2.00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, >
Jan 14 10:45:14 sai-precision3440 ddcutil[7384]: busno=5, Feature 0xdd should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x64 sh=0x00 sl=0x64
Jan 14 10:45:14 sai-precision3440 ddcutil[7384]: busno=5, Feature 0x41 should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x64 sh=0x00 sl=0x64
Jan 14 10:45:14 sai-precision3440 ddcutil[7384]: busno=5, Feature 0x00 should not exist but ddc_get_nontable_vcp_value() succeeds, returning mh=0x00 ml=0x64 sh=0x00 sl=0x64
...(repeats)

This repeated thousands of time in my last boot. For now, disabling the brightness slider makes it work.

To Reproduce
Steps to reproduce the behavior:

  1. Enable brightness setting in panel
  2. check journalctl logs

Expected behavior
Logs not being flooded.

Desktop (please complete the following information):
image

It might be specific to my build (using nvidia) as I did not notice this in my laptop, but I will look into it soon in sometime and see if I can fix it. I will report back soon. I also support the idea of #374, maybe while fixing this bug I can incorporate a feature to add a custom script as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant