No joy...
In keeping with other InputClass entries, I used this format (MatchDriver rather than Driver...could be a problem I suppose) and also tried with leaving out the (0471:0815) detail:
Section "InputClass"
Identifier "MCE USB Keyboard mimic blacklist"
MatchProduct "Philips (or NXP) eHome Infrared Receiver (0471:0815)"
MatchDriver "mceusb"
Option "Ignore" "on"
EndSection
Verified the drive name really is mceusb (Port 2: Dev 2):
m@m-G6:~$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=mceusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 2: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 2: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
and even verified with
Xorg pages that "on" is a valid boolean:
Boolean options may optionally have a value specified. When no value is specified, the option’s value is TRUE. The following boolean option values are recognised as TRUE:
1, on, true, yes
So, short of starting to pour through reams of logs, I'm stumped...maybe my test isn't valid...?
b