3.8 kernel breaks irexec

[xavier]

Problem: lirc hangs forever when I have a lircrc file when I use 3.8. 3.7 and previous kernels worked fine on Ubuntu 12.04 where I originally did some tests.

How to reproduce:
(1) Start 13.04 live cd
(2) sudo apt-get install lirc
(3) sudo nano /etc/lirc/lircrc
(4) copy your config, here is mine:
begin
#blabla
remote = devinput
button = KEY_POWER
prog = irexec
repeat = 0
config = python /home/script.py
end

More informations on how I found the problem: http://ubuntuforums.org/showpost.php?p=12502459&postcount=1
More informations on why I had to try the latest kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094904

All the informations concerning my 12.04 installation are available here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094904
I didn't take time to get outputs from the live cd. I used the daily live cd available on the 10th of february.
---
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
DistroRelease: Ubuntu 12.04
MarkForUpload: True
Package: linux (not installed)
Tags: precise
Uname: Linux 3.8.0-030800rc7-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1124581

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[xavier (s.xavier)]

apport information

[xavier (s.xavier)]

apport-collect 1124581 wasn't done on the live cd. It was done on 12.04 + 3.8rc7 kernel.

[Josh Rosenberg (7-launchpad-desh-info)]

I suspect the patch at http://forums.gentoo.org/viewtopic-t-960130-start-0.html#7313702 may help, but I don't know enough about compiling kernel modules to test this myself.

[penalvch (penalvch)]

xavier, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]