Created attachment 929989 [details] "w_scan -c GB -x -I /usr/share/dvb/dvb-t/uk-Sudbury" output Description of problem: "w_scan -x" reads wrong multiplex frequencies from the NIT data and writes out nonsense tuning data that doesn't match the initial tuning data. I don't know if this is just bad data from the Sudbury transmitter or some parsing weirdness, but e.g. scandvb from the dvb-apps package sees the same wrong frequencies when scanning for services. Version-Release number of selected component (if applicable): w_scan-20140118-1.fc19.x86_64 dtv-scan-tables-0-5.20140309git177b522.fc19.noarch How reproducible: $ w_scan -c GB -x -I /usr/share/dvb/dvb-t/uk-Sudbury reads weird multiplex frequencies out of the NIT tables. These frequencies don't seem to correspond to any local multiplex,and trying to tune to them gets absolutely no result. (By comparison, tuning to the very distant and weak Bluebell Hill transmitter at least gets enough signal to read back the multiplex frequencies). w_scan does successfuly find services on the real frequencies (those in the initial tuning data) however. Additional info: Note that scanning of the other local transmitter (Crystal Palace) succeeds without issue for w_scan-20140118-1.fc19.x86_64, but see bug #1133240 for problems with the latest version. The installed dtv-scan-tables is slightly out of data compared to upstream, but there's absolutely no change for the Sudbury transmitter, iirc.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.