https://bugs.kde.org/show_bug.cgi?id=476375
Sven <sven...@web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sven...@web.de
--- Comment #25 from Sven <sven...@web.de> ---
I have the same problem since the Update of ddcutil and powerdevil and tried
all 3 workarounds in the comments. When I edit the desktop file Powerdevil
still fails to start a few times but then the loop stops eventually. If I
increase the timeout time only the libddcutil errors below are present. With
the downgraded versions no error messages occur regarding this bug. So
downgrading currently seems the best option for me.
the repeating entries in my systemd journal log with Powerdevil 5.27.9-2 and
ddcutils 2.0.0-1:
Nov 20 16:18:43 xxx systemd[745]: Failed to start Powerdevil.
Nov 20 16:18:43 xxx systemd[745]: plasma-powerdevil.service: Failed with result
'timeout'.
Nov 20 16:18:43 xxx systemd[745]: plasma-powerdevil.service: start operation
timed out. Terminating.
Nov 20 16:18:42 xxx libddcutil[15006]: busno=6, 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)]
Nov 20 16:18:40 xxx libddcutil[15006]: busno=3, sleep-multiplier = 2,00.
Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in
ddc_write_read_with_retry, causes: DDCRC_READ_ALL_ZERO(10)]
Nov 20 16:18:38 xxx org_kde_powerdevil[15006]: org.kde.powerdevil:
org.kde.powerdevil.backlighthelper.brightness failed
Nov 20 16:18:38 xxx org_kde_powerdevil[15006]: org.kde.powerdevil:
org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds
are not supported by the kernel for this hardware"
I experimented a bit with ddcutil and got these infos:
'ddcutil detect' in version 1.4.1
No /dev/i2c devices exist.
ddcutil requires module i2c-dev.
'ddcutil detect' in version 2.0.0 (i removed my monitor details)
Invalid display
I2C bus: /dev/i2c-3
DRM connector: card0-HDMI-A-1
EDID synopsis:
Mfg id: xxx
Model: xxx
Product code: xxx
Serial number:
Binary serial number: xxx
Manufacture year: xxx
DDC communication failed. (getvcp of feature x10 returned
Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes:
DDCRC_READ_ALL_ZERO(10)])
DRM reports the monitor is disabled.
Invalid display
I2C bus: /dev/i2c-6
DRM connector: card0-DP-2
EDID synopsis:
Mfg id: xxx
Model: xxx
Product code: xxx
Serial number: xxx
Binary serial number: xxx
Manufacture year: xxx
DDC communication failed. (getvcp of feature x10 returned
Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes:
DDCRC_DDC_DATA(10)])
DRM reports the monitor is disabled.
It looks like ddcutils 2.0 now also lists my previously not recognized displays
and prints that communication error. 'ddcutil vcpinfo' says that 'feature x10'
is the brightness control support. Since both my monitors don't support that
feature, i think that error message is probably correct. But maybe this error
could be the reason why Powerdevil fails to start, since it also shows up in my
systemd journal shortly before Powerdevil fails.
--
You are receiving this mail because:
You are watching all bug changes.
