Federico Di Pierro

1: Thanks, fixed! It looks gorgeous now! 2,3: I'm looking forward to them :) 4: Yes, probably is a packaging issue, gonna report on aur. Thank you very much!

Moreover, this is just a plain "run program; wait; ctrl-c it (a signalfd is in place, so clean exit)". It seems like there is some library init function marked with...

I see; even if i know they are not proper "memleaks", i always find it a good design to actually free memory, even before program's exit. But that's me, and...

Hi! My use case is for https://github.com/FedeDP/Clightd; it exposes a Backlight dbus api to get/set backlight level, and when built with ddc support, it uses libddcutil. At the moment it...

Hi @rockowitz! Seeing your new release had a ddca_redetect_displays(), i implemented a timeout oriented hotplug mechanism, ie: every 30s my application calls ddca_redetect_displays() to keep its own list updated. It...

Hi @rockowitz ! Thanks for the quick response! It seems like most of them are now gone :) Unfortunately there is still one persisting, and its memory usage is growing...

Hi @rockowitz ! Thanks for your work! I noticed some more memleaks, thus i fixed them. I opened the https://github.com/rockowitz/ddcutil/pull/231 PR on top of 1.2.1-dev branch.

I merged the commits you pushed today in my branch; and now the only memleak that valgrind detects is about the pthread created in ddc_start_watch_displays() that lingers around. No problem...

Hi @rockowitz ! Didn't want to bother you with a new issue; moreover i don't even know if this is an issue! On my [Clightd](https://github.com/FedeDP/Clightd) project i am seeing a...

Hi! While it seems like a working solution, i am more keen to understand why is that even happening in the first place; i mean, this is not a bug...