[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 TraceyC changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 Nate Graham changed: What|Removed |Added CC|[email protected] | -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 postix changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 --- Comment #4 from Jakob Petsovits --- Comment #0 is confusing, because backlighthelper is only for internal (i.e. laptop) displays, but the actual bug report is clearly about an external monitor - connected to a desktop PC, which doesn't have an internal backlight display. So backlighthelper failing is entirely expected. We're interested in DDC happenings here. The attached log from Comment #0 shows that the monitor named "LG IPS FULLHD" is indeed found by PowerDevil with a brightness of 60 out of 100. The log from Comment #1 shows an error instead, the relevant lines are these (removing time, hostname & powerdevil unit prefix): > busno=2, sleep-multiplier = 2.00. Testing for supported feature 0x10 > returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: > DDCRC_DDC_DATA(10)] > Library initialization complete. > org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback > org.kde.powerdevil: [DDCutilDetector]: Check for monitors using > ddca_get_display_refs()... > org.kde.powerdevil: [DDCutilDetector]: 0 display(s) were detected The first line looks the most relevant, it's printed by libddcutil itself and talks about an error involving the brightness feature (0x10) before any other stuff starts failing. I'd have to get more familiar with DDC/CI and this part of libddcutil in order to analyze this any further. (In reply to Nate Graham from comment #2) > Possibly the same as Bug 482713? Possibly. The symptoms look the same, although without a better idea about the root cause it's hard to tell. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 --- Comment #3 from Debayan Sutradhar --- > Possibly the same as Bug 482713? Could be.. i am not sure. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 Nate Graham changed: What|Removed |Added CC||[email protected], ||[email protected] See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482713 --- Comment #2 from Nate Graham --- Possibly the same as Bug 482713? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 Debayan Sutradhar changed: What|Removed |Added Keywords||qt6, regression, wayland CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491605] backlighthelper.brightness display probe fails on Wayland
https://bugs.kde.org/show_bug.cgi?id=491605 --- Comment #1 from Debayan Sutradhar --- Created attachment 172530 --> https://bugs.kde.org/attachment.cgi?id=172530&action=edit sudo journalctl --boot -2 (after apply 3s delay) -- You are receiving this mail because: You are watching all bug changes.
