FS#46457 - [lirc] need rebuilt for kernel 4.2?

Attached to Project: Arch Linux
Opened by Andrew Gaydenko (student975) - Monday, 28 September 2015, 12:21 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 07 November 2015, 14:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Hi!

After today kernel update from 4.1 to 4.2 lirc serial driver works with errors (not-repeatable commands are treated as repeatable). Need rebuilt?
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 07 November 2015, 14:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  lirc 1:0.9.3.a-1
Comment by patrick (potomac) - Monday, 28 September 2015, 14:59 GMT
I notice also another problems with lirc-1:0.9.3-1 :

- the start of KDE 4.x is very slow, the boot stops for 30 seconds

- when I exit KDE there is a problem : systemd stops for 1m30 seconds with the message "a stop job is running for lircd"

and when I see in journalctl I see these messages :

lircd-0.9.3[554]: Info: Initial device: /dev/lirc0
lircd-0.9.3[554]: Debug: No device found: /sys/class/rc/rc0/lirc0
lircd-0.9.3[554]: Debug: No device found: /sys/class/rc/rc1/lirc0
lircd-0.9.3[554]: Info: Initial device: /dev/lirc0
lircd-0.9.3[554]: Debug: No device found: /sys/class/rc/rc0/lirc0
lircd-0.9.3[554]: Debug: No device found: /sys/class/rc/rc1/lirc0
lircd-0.9.3[554]: Warning: Running as root
lircd[554]: lircd-0.9.3[554]: Warning: Running as root
lircd-0.9.3[554]: Info: Using remote: LeadTekWinfastDTV1000.
lircd[554]: lircd-0.9.3[554]: Info: Using remote: LeadTekWinfastDTV1000.
Comment by patrick (potomac) - Monday, 28 September 2015, 15:08 GMT
If I downgrade to lirc 1:0.9.2.a-1 then all is Ok, no bugs, no slow boot, no error message with systemd,

so there is a problem with lirc-1:0.9.3-1
Comment by patrick (potomac) - Monday, 28 September 2015, 15:38 GMT
rebuilding the lirc package doesn't solve the problem,

it's seems an upstream bug
Comment by Andrew Gaydenko (student975) - Monday, 28 September 2015, 17:27 GMT
@patrick, have tried 0.9.2.a - yes, it does work for me also.
Comment by patrick (potomac) - Monday, 28 September 2015, 17:55 GMT
I found another workaround by changing my configuration file with another configuration, there is no bugs with 0.9.3 if I use a different configuration file for my leadtek winfast DTV1000 remote control :

https://www.mythtv.org/wiki/Winfast_DTV1000_remote

@Andrew Gaydenko : you can try also to change something in your configuration in order to see if it can help with the 0.9.3 version of lirc,

maybe the 0.9.3 version uses a different syntax for the configuration file, new keywords for example
Comment by Andrew Gaydenko (student975) - Monday, 28 September 2015, 18:05 GMT
@patrick, thanks, I will dig in and report.
Comment by Andrew Gaydenko (student975) - Tuesday, 29 September 2015, 09:13 GMT
I haven't found any configuration changes I must follow.

I have tried to recreate lircd.conf from the beginning (that is using irrecord utility), and it generates something very strange (say, 'bits 64' for 13 bit RC). I have tried to build 0.9.3 from sources with the same result.
Comment by Andrew Gaydenko (student975) - Tuesday, 29 September 2015, 13:36 GMT
Also, I have tried 0.9.3 with linux-lts, and the issue still exists. So, as patrick has guessed earlier, I also guess the issue is an upstream one. Task title must be changed, but not sure how to name it.
Comment by Andrew Gaydenko (student975) - Wednesday, 28 October 2015, 10:12 GMT
The issue was resolved by upstream about two weeks ago. So the issue must be closed, I guess.

Unfortunately, the package is still flagged to be updated in Arch repo. Can anybody from the Arch team update it? Thanks!
Comment by John (graysky) - Saturday, 07 November 2015, 12:14 GMT Comment by Andrew Gaydenko (student975) - Saturday, 07 November 2015, 13:39 GMT
It's OK for mew to close, thanks!

Loading...