package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[alvaro osuna arciniegas]

Thanks a lot....

Alvaro Osuna
Call me Tony

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: lirc 0.9.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
Date: Sun Jul 21 19:31:42 2013
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2013-07-21 (0 days ago)
InstallationMedia: This
MarkForUpload: True
SourcePackage: lirc
Title: package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[alvaro osuna arciniegas (valosuna100)]

I have the new vertion of ubuntu 13.04.... install pass two days
ago... I 'm very happy to used....Really is better than the 12.04, and
offcourse... I really love linux, Ubuntu comunity.

I hake microsoft and windows 7 is another scam lake the other's edition.
Also i used a tablet with android 4.1 .....Ubuntu gonna launch a
vertion for Cellphones and tablets???? I read the news at facebook.
Waiting for make the change in the Tablet and to help to promotional
these gorgeus software.

Best Regards, for you Seth,....
and all of a proud community.

Sincerly Yours and thanks again....

Alvaro A. Osuna Arciniegas

2013/7/21, Seth Arnold <email address hidden>:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We appreciate the difficulties you are facing, but this appears
> to be a "regular" (non-security) bug. I have unmarked it as a security
> issue since this bug does not show evidence of allowing attackers to
> cross privilege boundaries nor directly cause loss of data/privacy.
> Please feel free to report any other bugs you may find.
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1203483
>
> Title:
> package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 128
>
> Status in “lirc” package in Ubuntu:
> New
>
> Bug description:
> Thanks a lot....
>
>
> Alvaro Osuna
> Call me Tony
>
> ProblemType: Package
> DistroRelease: Ubuntu 13.04
> Package: lirc 0.9.0-0ubuntu3
> ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
> Uname: Linux 3.8.0-26-generic i686
> NonfreeKernelModules: nvidia
> ApportVersion: 2.9.2-0ubuntu8.1
> Architecture: i386
> Date: Sun Jul 21 19:31:42 2013
> ErrorMessage: subprocess installed post-installation script returned error
> exit status 128
> InstallationDate: Installed on 2013-07-21 (0 days ago)
> InstallationMedia: This
> MarkForUpload: True
> SourcePackage: lirc
> Title: package lirc 0.9.0-0ubuntu3 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 128
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1203483/+subscriptions
>

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alec Leamas (leamas-alec)]

This is fixed in new version 0.9.4b, now in zesty - experimental.

[kirke (tallbear44)]

I'm on 14.04 LTS and found this as a duplicate of Bug #1497266 reported by Lin Yu Han on 2015-09-18. I'm wondering why the fix for this bug has not been tested and made available in more than the zesty (experimental) repository? Alec had a fix 2 years ago:

Launchpad Janitor (janitor) wrote on 2016-11-01: #4
This bug was fixed in the package lirc - 0.9.4c-4

14.04 is still at 0.9.0-0ubuntu5, which does not install. Everyone on the Long Term Support release with a need for lirc is vulnerable. I attempted 'apt-get install inputlirc' naked, but that brings lirc and this failure too.

I've tried to avoid using lirc, but receive no (EV_KEY) key events in 'ir-keytable -t' output.

root@dor:/home/kirke/DOR# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event10) with:
 Driver mceusb, table rc-rc6-mce
 Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
 Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
 Name: Media Center Ed. eHome Infrared
 bus: 3, vendor/product: 1784:0011, version: 0x0100
 Repeat delay = 500 ms, repeat period = 125 ms
root@dor:/home/kirke/DOR# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1551891292.693694: event type EV_MSC(0x04): scancode = 0x1f3f
1551891292.693694: event type EV_SYN(0x00).
1551891292.714638: event type EV_MSC(0x04): scancode = 0xb70076
1551891292.714638: event type EV_SYN(0x00).
1551891292.739634: event type EV_MSC(0x04): scancode = 0x1f3f
1551891292.739634: event type EV_SYN(0x00).
1551891292.759642: event type EV_MSC(0x04): scancode = 0xb70076
1551891292.759642: event type EV_SYN(0x00).
1551891292.784694: event type EV_MSC(0x04): scancode = 0x1f3f
1551891292.784694: event type EV_SYN(0x00).
1551891292.884699: event type EV_MSC(0x04): scancode = 0xb70076
1551891292.884699: event type EV_SYN(0x00).

Above is what I see after pressing the OK (Select) button.

I have the same remote and IR receiver working fine in the living room with lirc untouched under a 2014 install. I want to transition both machines to 18.04, but have no confidence I'll
have a working remote control for mythtv.

Apparently, I've removed and purged lirc in a way that is confusing packaging software's post install script.