Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33227 - [v4l-utils] breaks mceusb
Attached to Project:
Arch Linux
Opened by Michael Zanetti (mzanetti) - Friday, 28 December 2012, 17:02 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 06 July 2015, 15:24 GMT
Opened by Michael Zanetti (mzanetti) - Friday, 28 December 2012, 17:02 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 06 July 2015, 15:24 GMT
|
DetailsDescription:
installing v4l-utils breaks mceusb remote Additional info: v4l-utils installs a udev rule that causes mceusb remotes with lircd to stop working (/usr/lib/udev/rules.d/70-infrared.rules) This has been in there for more than a year now. I knew how to workaround (removing v4l-utils) but its starting to get annoying because v4l-utils is pulled as a dependency on every update now. Steps to reproduce: - Set up lircd with an mceusb remote for use with xbmc or mythtv or whatever. - install v4l-utils - reboot (or re-run udev rules somehow) => your remote doesn't work any more until v4l-utils is removed. Most likely this has to do with the IR remotes producing keyboard keycodes now. However, for many use cases this isn't working quite as good as the old lircd socket solution. v4l-utils should not just destroy the old way, but rather offer a possibility to switch (or add a check if this udev rule should be executed depending on system configuration) |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 06 July 2015, 15:24 GMT
Reason for closing: No response
Additional comments about closing: Reporter is no longer on Arch and there's no response from the one other person who is following.
Monday, 06 July 2015, 15:24 GMT
Reason for closing: No response
Additional comments about closing: Reporter is no longer on Arch and there's no response from the one other person who is following.
If you suffer from the same issue, please add a vote to this bug to hopefully make it more visible and/or increase its priority.
Thanks again.
Pablo.