Bug#788100: /usr/bin/w_scan: w_scan systematically fails due to wrong updating of transponders

Eric Valette eric2.valette at orange.com
Mon Jun 8 13:36:07 UTC 2015


Package: w-scan
Version: 20140727-1
Severity: important
File: /usr/bin/w_scan

Dear Maintainer,

Trying to use tvheadend 4.1, I restarted to use w_scan to ge the initial
list of muxes and discovered  (or rediscovered) that recent version of
w_scan doe not work in my location (used to work before).

Doing the_scan, it correctly find the first transponder frequency (474000)
but the using the -v -v option I see a message syaing that it updates the
transponder to a new transpondeur that is obviously invalid:

Beginning of trace:

./w_scan -v -v -c FR -f t 
w_scan version 20140727 (compiled for DVB API 5.10)
using settings for FRANCE
DVB aerial
DVB-T FR
scan type TERRESTRIAL, channellist 5
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
   check Afatech AF9033 (DVB-T):
           DVB-T
	/dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Afatech AF9033 (DVB-T)": good :-)
   check Afatech AF9033 (DVB-T):
           DVB-T
	/dev/dvb/adapter1/frontend0 -> TERRESTRIAL "Afatech AF9033 (DVB-T)": good :-)
Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Afatech AF9033 (DVB-T)' supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
FREQ (174.00MHz ... 858.00MHz)


...
...

Where the problem is:

        updating transponder:
           (QAM_64   f = 474000 kHz I999B8C999D999T999G999Y999 (8442:8442:1)) 0x0000
        to (QAM_64   f = 4294967 kHz I999B8C999D0T8G8Y0 (8442:8442:1)) 0x405A
          ================= list_transponders() =======================
          new_transponders(000): QAM_64   f = 4294967 kHz I999B8C999D0T8G8Y0 (8442:8442:1)

where the frequency change from 474000 kHz to 4294967 kHz which is of
course out of range, so when it does the second pass to output the file
it barks and fails. A simple check would be to validate the new frequency
at least to see if it is still in the list of authorized frequencies for the
device...

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages w-scan depends on:
ii  libc6  2.21-0experimental0

w-scan recommends no packages.

w-scan suggests no packages.

-- no debconf information



More information about the pkg-vdr-dvb-devel mailing list