Open AurelienDevGames opened 1 month ago
Ugh. I thought I had posted an extensive response to go along with the labels assigned 4 days ago. In summary:
The immediate cause of the crash had been fixed by commit 196f3 in branch 2.1.5-dev, in response to issue #405. This occurred when the device name property was not set when the udev rule in 60-ddcutil.rules was processed.
The rule gives the logged on user RW permission to any /dev/usb/hiddev* device associated with a monitor that uses USB communication to communicate with its Virtual Control Panel, and which adheres to the USB Device Class Definition for Human Interface Devices. Such monitors have proven extremely rare.
With commit d7416 in branch 2.1.5-dev, ddcutil chkusbmon returns immediately if option disable-usb has been specified in the ddcutil configuration file.
If ddcutil is built with configure option --enable-usb=no, ddcutil is built without support for USB communication. In this case command ddcutil chkusbmon is not built, and the udev rule is not installed.
As an alternative to building from branch 2.1.5-dev, you can simply delete file /usr/lib/udev/rules.d/60-ddcutil-usb.rules.
Hi,
Without fail if I restart my system with my Thrustmaster Rudder Pedals connected, ddcutil crashes the boot sequence forcing me to power down manually. This does not happen if it is a simple power up, only on restart.
I have a multi monitor setup on Fedora 40 KDE.
Ddcutil-interrogate verbose ddcutil-interrogate.txt
inxi -FGxx
journalctl -xb-1
coredump.zip