Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24354 - [mythtv] 1:0.24.1-1 breaks IVTV tuners
Attached to Project:
Community Packages
Opened by Matt Daubenspeck (mellofone) - Thursday, 19 May 2011, 19:45 GMT
Last edited by Jonathan Conder (PirateJonno) - Wednesday, 01 June 2011, 19:47 GMT
Opened by Matt Daubenspeck (mellofone) - Thursday, 19 May 2011, 19:45 GMT
Last edited by Jonathan Conder (PirateJonno) - Wednesday, 01 June 2011, 19:47 GMT
|
DetailsDescription: Upgrading Mythtv on x86_64 from arch package mythtv 1:0.24-2 to 1:0.24.1-1 seems to break IVTV tuner support. After upgrading and a backend restart, none of my IVTV (PVR500 and PVR150) are displayed as a tuner. Trying to re-add them, the option of selecting a tuner type of IVTV is no longer an option. The cards themselves are shown as a generic MPEG file tuner, but do not show up in the tuner list. My network HDHomeRun tuners are unaffected and work perfectly.
Reverting to 1:0.24-2 brings the cards back and everything functions normally. I checked the upstream MythTV 0.24.1 release notes and can't find anything that would remove this option. The main mythbackend log shows nothing, even with all of the debug options turned on. |
This task depends upon
Closed by Jonathan Conder (PirateJonno)
Wednesday, 01 June 2011, 19:47 GMT
Reason for closing: Fixed
Wednesday, 01 June 2011, 19:47 GMT
Reason for closing: Fixed
http://www.mythtv.org/pipermail/mythtv-users/2011-May/315477.html
I have included all the modified build stuff. All you need to do is recompile and you should be good to go.
I can confirm that the package build that Robert attached does fix the problem.