https://bugs.kde.org/show_bug.cgi?id=494522
--- Comment #20 from Jakob Petsovits <jpe...@petsovits.com> --- (In reply to Devin Lin from comment #19) > Indeed, running `ddcutil --display=1 setvcp 10 50` causes the display to > crash after a fresh reboot of the monitor. Interestingly enough, it prints > `Display not found` > > It is inconsistent though in that if you change some settings (ex. setting > the refresh rate) and then run the command, it doesn't crash anymore, but > instead fails with: `Verification failed for feature 10` In that case, it may pay off to discuss this behavior on the ddcutil issue queue, at https://github.com/rockowitz/ddcutil/issues. I don't see an issue specifically for the Samsung G5, however there is some discussion about "Verification failed for feature 10" at https://github.com/rockowitz/ddcutil/issues/323, seen for various different monitors. Let's not mark this RESOLVED UPSTREAM though until we know that ddcutil is actually in a position to deliver any kind of fix for this. If it isn't, the fix will have to be a checkbox to disable hardware brightness for this monitor despite the hardware claiming that it can do it. -- You are receiving this mail because: You are watching all bug changes.
