Looks like Ubuntu kernel will need to be patched on its own - Upstream developer agreed that the proposed fix in this bug is proper for Ubuntu since there no easy way to pull from upstream since code has changed:

(10:33:06 AM) j-rod: that code did go upstream, but has subsequently changed
(10:36:13 AM) j-rod: so the streamzap thing can be fixed in the code in the ubuntu kernel by just moving rc5sz matching before rc5
(10:36:46 AM) j-rod: but store_protocol() changed a ton upstream since what was pulled in to the ubuntu kernel, so its not a fix that applies upstream

First was that the /etc/init.d/lirc file had both rc5sz and lirc enabled and both were reporting the Streamzap remote keys.
However, even after this file is fixed to add rc5sz (this is the correct spelling, rc5-sz and rc-5-sz are wrong) to the disable list, it doesn't get disabled.

This second error is in the ir-sysfs.c file which is part of the kernel code. This is the code that reads and processes the /etc/init.d/lirc file. This code has a bug which causes it to not correctly process the "rc3sz" entry. This can be fixed by reversing the checks for rc5 and rc5sz.

I suggest the ir_core and related backports to the 10.10 Ubuntu kernel be removed as a fix to this issue. They seem to be added too early in the development without making sure the pieces play together well first. Mythbuntu is essentially broken due to these patches - a stock Hauppauge 150 does not work out of the box.

I am new to launchpad. This bug affects me, I waited to upgrade to 10.10 until it was released and the official Mythbuntu page endorsed it. The Streamzap remote was one of the most endorsed remotes for Mythtv by various distributions so I bought it.

How do I fix this now? Where can I find instructions on installing patches and scripts?

Here's another workaround. I had to recompile my kernel anyway to re-enable ALSA OSS emulation (see https://bugs.launchpad.net/bugs/579300 for the full story if you're interested). Disabling CONFIG_IR_STREAMZAP in the kernel (Device Drivers --> Multimedia Support --> Streamzap PC Remote IR Receiver) fixed the problem for me, allowing the Streamzap drivers included in lirc to work uncontested.

I've setup and tested Streamzap with Ubuntu 10.10 using LIRC and by disabling Streamzap Xinput Keyboard created by Xorg from UDEV. All the instructions are here, it is possible this will work for MythTV people too.

Solves the issue perfectly for me. Also, this method can be built into a debian package for mythbuntu. It would be trivial to build a package that would resolve this issue as it would only include pasting the above file into the correct directory and rebooting the xserver.

If disabling the STREAMZAP kernel config option worked for some of you then it is possible that just blacklisting that module would help. Creating a file named '/etc/modprobe.conf/streamzap.conf' containing 'blacklist streamzap' should prevent that module loading. If those of you affected could test that and report back here. Thanks.

To recap my understanding here: To fix the bug in Maverick we need:
1. The patch from comment #8 in the kernel to enable protocol changes for rc5sz (I made some test packages for -generic and put those to http://people.canonical.com/~smb/lp663651/)
2. The changes from comment #2 (but with rc5-sz changed into rc5sz)

So would 1. and 2. be all needed or is the 90-streamzap.conf file still needed in that case?