Page MenuHomeSolus

Fixes #T8734 Can't apply udev rules when ckb-next-daemon is running
ClosedPublic

Authored by STiAT on Tue, May 12, 3:44 PM.

Details

Summary

usysconf fails reloading udev rules (udevadm trigger) when ckb-next-daemon is running.
As written in the bug report this is a kernel issue, and the ckb-next developers
decided to work around it since it takes time for kernel maintainers to fix and for
the kernel to appear downstream on the distributions.

I decided to apply the relevant patches to 0.4.2 to fix this issue, this patches should not
be necessary any longer once 0.4.3 is released.

Test Plan
  • Update the package (with a corsair peripheral)
  • restart ckb-next-daemon
  • run udevadm trigger
  • No more error messages are displayed, thus, usysconf won't complain any longer.

Diff Detail

Repository
R520 ckb
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

STiAT created this revision.Tue, May 12, 3:44 PM
STiAT requested review of this revision.Tue, May 12, 3:44 PM
DataDrake accepted this revision.Wed, May 13, 5:16 AM
DataDrake added a subscriber: DataDrake.

LGTM. Thanks!

This revision is now accepted and ready to land.Wed, May 13, 5:16 AM