me-tv app on 18.04 relaease

Asked by peter b on 2018-05-02

- no me-tv app on ubuntu 18.04 bionic repositories to date
- kindly, any idea when available?
or
- any install instructions/how to?

- commands output:

w_scan -fa -c CA
w_scan -fa -c CA
w_scan version 20170107 (compiled for DVB API 5.10)
using settings for CANADA
ATSC
VSB US/CA, DVB-T TW
scan type TERRCABLE_ATSC, channellist 1
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.
 /dev/dvb/adapter0/frontend0 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
Using TERRCABLE_ATSC frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.10
frontend 'Auvitek AU8522 QAM/8VSB Frontend' supports
INVERSION_AUTO
8VSB
QAM_64
QAM_256
FREQ (54.00MHz ... 858.00MHz)
..
..
(time: 04:25.825) dumping lists (13 services)
..
CHCH-DT;(null):479000:M10:A:0:49:52=eng;52:0:0:3:0:0:0
TVO;(null):503000:M10:A:0:49=2:52=eng,53=eng;52,53:0:0:1:0:0:0
TORONTO CBLT-DT;(null):509000:M10:A:0:49=2:52=eng,53=enm;52,53:0:0:3:0:0:0
ONTARIO CBLFT-DT;(null):539000:M10:A:0:49:52=fre,53=frm;52,53:0:0:3:0:0:0
Bounce;(null):581000:M10:A:0:65=2:68=eng;68:0:0:4:0:0:0
WIVB-HD;(null):581000:M10:A:0:81:84=eng,85=spa;84,85:0:0:5:0:0:0
LAFF;(null):581000:M10:A:0:97=2:100=eng;100:0:0:6:0:0:0
WNLO-HD;(null):581000:M10:A:0:49:52=eng,53=spa;52,53:0:0:3:0:0:0
CITS-HD;(null):605000:M10:A:0:49:51=eng,52=enm;51,52:0:0:1:0:0:0
CIII-HD;(null):635000:M10:A:0:49=2:52=eng,53=eng;52,53:0:0:1:0:0:0
CIII-SD;(null):635000:M10:A:0:65=2:68=eng,69=eng;68,69:0:0:2:0:0:0
CITYTV;(null):653000:M10:A:0:33:36=eng,37=fre;36,37:0:0:2:0:0:0
CFMT;(null):671000:M10:A:0:33:36=eng,37=fre;36,37:0:0:2:0:0:0
Done, scan time: 04:25.825

lsusb
..
..
Bus 005 Device 002: ID 2040:7200 Hauppauge
..

NOTE: on 16.04 flawless.

Thank you.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2018-05-03
Last reply:
2018-05-04

I suggest you report a bug

Manfred Hampl (m-hampl) said : #2

see the publication history in https://launchpad.net/ubuntu/+source/me-tv/+publishinghistory

Removal requested on 2016-07-26.

(From Debian) RoQA; RC buggy; orphaned since 2014; last released upstream in 2012; Debian bug https://bugs.debian.org/755451

peter b (b1pete) said : #3

thanks to all; hope it's not the end of it, maybe somebody will pick it up and revive it; nice app, worked v well, slick, never had problems.

Any experience with similar type app pls?
any recommendations?

it's v nice to switch now and then to a bit of entertainment, relax for 5-10minutes.

peter b (b1pete) said : #4

on 18.04
tvtime app at approx 75% in install procedure, after config screen launched crushed; report auto created and submitted; looks like bug #1768195 package tvtime 1.0.2-14ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

valid/affects 18.04 too.

Manfred Hampl (m-hampl) said : #5

For diagnostic purposes:

1. What output do you receive for the commands

uname -a
lsb_release -crid
sudo dpkg --audit

2. For debugging the post-installation script issue the command

sudo gedit /var/lib/dpkg/info/tvtime.postinst

and modify the first line:
change
#! /bin/sh
into
#! /bin/sh -x
save the file and close the editor.

and finally issue the command

sudo dpkg --configure -a

and check for an error message (or copy/paste all output into this question document)

peter b (b1pete) said : #6

thanks Manfred; commands output - below:

uname -a
Linux peter-18 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

************************************************************

lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

****************************************************************

sudo dpkg --audit
[sudo] password for peter:
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
 tvtime analog television display application

**********************************************************************

  sudo gedit /var/lib/dpkg/info/tvtime.postinst

** (gedit:2279): WARNING **: 11:30:33.136: Set document metadata failed: Setting attribute metadata::gedit-spell-language not supported

** (gedit:2279): WARNING **: 11:30:33.137: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported

** (gedit:2279): WARNING **: 11:30:43.031: Set document metadata failed: Setting attribute metadata::gedit-position not supported

********************************************************************

sudo dpkg --configure -a
Setting up tvtime (1.0.11-1) ...
+ set -e
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/tvtime.postinst configure
+ set -e
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z ]
+ exec
+ [ ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ setuid
+ db_get tvtime/setuid
+ _db_cmd GET tvtime/setuid
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/setuid
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=false
+ return 0
+ [ -x /usr/bin/tvtime ]
+ [ false = false ]
+ dpkg-statoverride --list /usr/bin/tvtime
+ chown root:root /usr/bin/tvtime
+ chmod u=rwx,go=rx /usr/bin/tvtime
+ suck_tvtime_xml
+ [ -f /etc/tvtime/debconf.tvtime.xml ]
+ [ -d /var/run/tvtime ]
+ CONFIGFILE=/etc/tvtime/tvtime.xml
+ db_get tvtime/norm
+ _db_cmd GET tvtime/norm
+ _db_internal_IFS=

+ IFS= sudo dpkg --configure -a
Setting up tvtime (1.0.11-1) ...
+ set -e
+ . /usr/share/debconf/confmodule
+ [ ! ]
+ PERL_DL_NONLAZY=1
+ export PERL_DL_NONLAZY
+ [ ]
+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/tvtime.postinst configure
+ set -e
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z ]
+ exec
+ [ ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ setuid
+ db_get tvtime/setuid
+ _db_cmd GET tvtime/setuid
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/setuid
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=false
+ return 0
+ [ -x /usr/bin/tvtime ]
+ [ false = false ]
+ dpkg-statoverride --list /usr/bin/tvtime
+ chown root:root /usr/bin/tvtime
+ chmod u=rwx,go=rx /usr/bin/tvtime
+ suck_tvtime_xml
+ [ -f /etc/tvtime/debconf.tvtime.xml ]
+ [ -d /var/run/tvtime ]
+ CONFIGFILE=/etc/tvtime/tvtime.xml
+ db_get tvtime/norm
+ _db_cmd GET tvtime/norm
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/norm
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=NTSC
+ return 0
+ NORM=NTSC
+ db_get tvtime/frequencies-ntsc
+ _db_cmd GET tvtime/frequencies-ntsc
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/frequencies-ntsc
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=Cable
+ return 0
+ FREQTABLE=us-cable
+ db_get tvtime/v4ldevice
+ _db_cmd GET tvtime/v4ldevice
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/v4ldevice
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=auto
+ return 0
+ V4LDEV=auto
+ db_get tvtime/vbidevice
+ _db_cmd GET tvtime/vbidevice
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/vbidevice
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=/dev/vbi0
+ return 0
+ VBIDEV=/dev/vbi0
+ db_get tvtime/processpriority
+ _db_cmd GET tvtime/processpriority
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/processpriority
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=-10
+ return 0
+ PRI=-10
+ db_stop
+ echo STOP
+ [ ! -f /etc/tvtime/tvtime.xml ]
+ tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10
+ exit 0
peter@peter-18:~$

+ printf %s\n GET tvtime/norm
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=NTSC
+ return 0
+ NORM=NTSC
+ db_get tvtime/frequencies-ntsc
+ _db_cmd GET tvtime/frequencies-ntsc
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/frequencies-ntsc
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=Cable
+ return 0
+ FREQTABLE=us-cable
+ db_get tvtime/v4ldevice
+ _db_cmd GET tvtime/v4ldevice
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/v4ldevice
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=auto
+ return 0
+ V4LDEV=auto
+ db_get tvtime/vbidevice
+ _db_cmd GET tvtime/vbidevice
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/vbidevice
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=/dev/vbi0
+ return 0
+ VBIDEV=/dev/vbi0
+ db_get tvtime/processpriority
+ _db_cmd GET tvtime/processpriority
+ _db_internal_IFS=

+ IFS=
+ printf %s\n GET tvtime/processpriority
+ IFS=

+ IFS=
 read -r _db_internal_line
+ RET=-10
+ return 0
+ PRI=-10
+ db_stop
+ echo STOP
+ [ ! -f /etc/tvtime/tvtime.xml ] just v quick passing through
+ tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10
+ exit 0
peter@peter-18:~$

- yes, a v quick look over procedure lines - just a humble opinion - maybe have w_scan procedure/command detect the TV signals first and then continue with app configuration??
- looking at the last line - that is where the install procedure stopped/aborted.

thank you - appreciate your help; great show, I'll do anything you ask, assist you to debug tvtime, get it 'on its feet' and run.

Manfred Hampl (m-hampl) said : #7

What do you get for the commands

sudo tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10

echo $?

peter b (b1pete) said : #8

peter@peter-18:~$ me/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10
bash: me/tvtime.xml: No such file or directory
peter@peter-18:~$ + exit 0
+: command not found
peter@peter-18:~$ peter@peter-18:~$
peter@peter-18:~$: command not found
peter@peter-18:~$ sudo tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC
[sudo] password for peter:
Sorry, try again.
[sudo] password for peter:
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/peter/.tvtime/tvtime.xml
Reading configuration from /etc/tvtime/tvtime.xml
peter@peter-18:~$

here it is; tx.

just a note - looked over w_scan command/manual just now - it looks very well written/thorough, it covers apparently all the 'angles' - country, analog, cable signals etc.

Manfred Hampl (m-hampl) said : #9

What do you now get for

sudo dpkg --configure -a

peter b (b1pete) said : #10

tx. - here it is

peter@peter-18:~$ sudo dpkg --configure -a
[sudo] password for peter:
peter@peter-18:~$

best regards.

Manfred Hampl (m-hampl) said : #11

Ok, the tvtime application seems to be finally installed.

Now try whether it works.

peter b (b1pete) said : #12

- yes Manfred, it installed without any errors, thank you

but....

- I launched it immediately after snap install finished; yes,
it does open all right,
can see the blue screen,
channel numbers that show on the window title bar as well as in bold on the screen
the up/down arrow keys advance the channel number

but.... on the screen 'no signal' message is all the time there, no image whatsoever regardless channel number.

so, restarted PC and re-launched tvtime app again

- still 'no cigar', same situation as above, no image at all..

just a thought that still lingers in my mind Manfred - sorry, i'm not at all the guru that knows everything but... my logic tells me that the app flow must have:

- v early in its procedure the bases set, identified so to speak as far as the channels availability so,
- the channel scanning procedure be completed, and, pending the results
- YES, channels found/available, store them, complete app install procedure -> SUCCESS, OR
- NO, channels NOT found/available, tell/notify the user NO channels found/available and stop/abort the procedure -> FAILURE

why I say all this? because when w_scan command is run it identifies the channels available v v well although it takes some time (in my case it took 4+minutes)

pls look at the above just as my '2 cents' contribution; thank you; cheers, for sure/convinced that you'll get to the bottom of it.

peter b (b1pete) said : #13

just a thought Manfred - does /var/lib/dpkg/info/tvtime.postinst file EDITED with #! /bin/sh -x previously have any bearing/significants when tvtime was reinstalled pls?

just checked it and is still there with that line edited.

Manfred Hampl (m-hampl) said : #14

1. The "#! /bin/sh -x " modification was my suggestion to find out at which part of the postinst script initially failed. It does not change anything on the logic but just turns on debug output.

2. When re-reading the output of your commands I see that you missed a part of a command. Maybe this has some influence on the configuration of tvtime.

sudo tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10

You have to copy/paste both lines at once.

3. I do not think that I can help further with setting up the application, because I do not have a TV card connected to my PC myself.

peter b (b1pete) said : #15

sorry, here it is: ...

peter@peter-18:~$ sudo tvtime-configure --configfile=/etc/tvtime/tvtime.xml --norm=NTSC --frequencies=us-cable --device=auto --vbidevice=/dev/vbi0 --priority=-10
[sudo] password for peter:
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/peter/.tvtime/tvtime.xml
Reading configuration from /etc/tvtime/tvtime.xml
peter@peter-18:~$

a thought crossed my mind Manfred - the more I look into this app - sure it would be v nice to have it run automatically without any additional input from user at install time; no doubt it can be done provided that all primary info - country, signal type, etc are identified and stored so the config can successfully complete and app run successfully

BUT ....

it can be set in an interactive mode, the user be prompted to provide that key info - country, signal type etc THEN asked to run w_scan command with all switches provided and store the output/properly configure the app

re your question - me-tv app was a v v well written app; any chance to revive it? port it to 18.04? ; I'll do the testing but first need it; can you make it available to me?

second thought - card/TV DEVICE availabilty - is it a big problem to get one for testing/working with it and getting ubuntu repository a nice app?

personal opinion just for you - if I'd be you I'll do all it takes to revive me-tv app - it proved itself, 16.04 is living proof; maybe talk with the maintainer/author?.

Manfred Hampl (m-hampl) said : #16

Just a note:

There is a command tvtime-scanner
Maybe it does similar thing as w_scan, but cooperates with tvtime

peter b (b1pete) said : #17

yes, after running for some 1hr the output below below

peter@peter-18:~$ tvtime-scanner
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/peter/.tvtime/tvtime.xml
Scanning using TV standard NTSC.
/home/peter/.tvtime/stationlist.xml: No existing NTSC station list "Custom".
videoinput-auto: using analog TV device /dev/video1
Scanning from 44.00 MHz to 958.00 MHz.
peter@peter-18:~$ z: - No signal

so, that tells it all; no comparison with w_scan command output.

personal opinion tvtime app as it stands today does not deliver; I'll just remove it. Maybe remove it from ubuntu repository too until worked some more and tested?

still thinking - me-tv becomes v appealing to be revived somehow? I'll be on vacation until the 20th of May; maybe some news then on this subject. Thank for all you've done, help. See you then. cheers, best.

Manfred Hampl (m-hampl) said : #18

I assume that you have to add some options and parameters to the tvtime-scanner command (and probably to the tvtime command as well), perhaps something like

tvtime-scanner --norm=NTSC --frequencies=us-cable --device=auto

If this fails with a similar error, then you have to try finding out what the device name for your TV adapter is, e.g. with commands like

ls -l /dev/vid*
ls -l /dev/dv*
ls -l /dev/dvb/*
ls -l /dev/dvb/*/*

and add the identified device to the command like

tvtime-scanner --norm=NTSC --frequencies=us-cable --device=/dev/dvb/adapter0/frontend0
or
tvtime-scanner --norm=NTSC --frequencies=us-cable --device=/dev/dvb/adapter0/dvr0

Additional question:
If this is a USB device:
Boot your system without the device and wait a few minutes for all startup processes to finish. Then plug in the device, wait half a minute and issue the command
dmesg | tail
This should show some messages about initialization of the device. Maybe this shows something useful.

peter b (b1pete) said : #19

thank you Manfred,

re: tvtime-scanner --norm=NTSC --frequencies=us-cable --device=auto

before using it wanted to know exactly the syntax/additional switches/options (NOTE: w_scan v well documented on manual)

searched for it - the command tvtime-scanner AND man tvtime-scanner -->> no luck so far; see below pls

*********************************************

re:
ls -l /dev/vid*
ls -l /dev/dv*
ls -l /dev/dvb/*
ls -l /dev/dvb/*/*

output:

peter@peter-18:~$ ls -l /dev/vid*
crw-rw----+ 1 root video 81, 0 May 4 09:47 /dev/video0
crw-rw----+ 1 root video 81, 1 May 4 09:47 /dev/video1
peter@peter-18:~$ ls -l /dev/dvb/*/*
crw-rw----+ 1 root video 212, 1 May 4 09:47 /dev/dvb/adapter0/demux0
crw-rw----+ 1 root video 212, 2 May 4 09:47 /dev/dvb/adapter0/dvr0
crw-rw----+ 1 root video 212, 0 May 4 09:47 /dev/dvb/adapter0/frontend0
crw-rw----+ 1 root video 212, 3 May 4 09:47 /dev/dvb/adapter0/net0
peter@peter-18:~$
peter@peter-18:~$ ls -l /dev/dvb/*
total 0
crw-rw----+ 1 root video 212, 1 May 4 09:47 demux0
crw-rw----+ 1 root video 212, 2 May 4 09:47 dvr0
crw-rw----+ 1 root video 212, 0 May 4 09:47 frontend0
crw-rw----+ 1 root video 212, 3 May 4 09:47 net0
peter@peter-18:~$ ls -l /dev/dv*
total 0
drwxr-xr-x 2 root root 120 May 4 09:47 adapter0
peter@peter-18:~$ man tvtime-scanner
No manual entry for tvtime-scanner
peter@peter-18:~$

***************************************

personal opinion - same as aired earlier - tvtime AND its tvtime-scanner companion need some attention --->> I would dearly love to use them but... pls take a look at man w_scan, v v well documented switches/options compared with NO man tvtime-scanner.

so, maybe time will 'heal' these misses somehow and happily get this tvtime app off the ground, make it run happily.

today I'm packing the suitcase and tomorrow leave; back on the 20th; thanks Manfred, talk with you then; maybe there'll be some good news then.

Manfred Hampl (m-hampl) said : #20

There are man pages for tvtime-scanner, see http://manpages.ubuntu.com/manpages/bionic/en/man1/tvtime-scanner.1.html
I am surprised to see that your system tells "No manual entry for tvtime-scanner"

peter b (b1pete) said : #21

just before I leave

peter@peter-18:~$ v4l2-ctl --list-devices
Hauppauge HVR950Q (usb-0000:00:10.0-1):
 /dev/video1
 /dev/vbi0

HD WebCam: HD WebCam (usb-0000:00:13.2-2):
 /dev/video0
**************************************

peter@peter-18:~$ tvtime-scanner -d /dev/video1
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/peter/.tvtime/tvtime.xml
Scanning using TV standard NTSC.
Scanning from 44.00 MHz to 958.00 MHz.
Checking 545.25 MHz:^C- No signal
 peter@peter-18:~$

I stopped it - By this frequency w_scan already found few channels, see first post

*************************************

lsusb --verbose

...

Bus 005 Device 002: ID 2040:7200 Hauppauge
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x2040 Hauppauge
  idProduct 0x7200
  bcdDevice 0.05
  iManufacturer 1
  iProduct 2
  iSerial 10

....
peter@peter-18:~$

pls see 'couldn't open device' --> ???

- just thinking Manfred - why 'reinvent the wheel' when there is one - w_scan that does an excellent job/verified/proven? my first post shows it; moreover - works excellently - me-tv on 16.04 flawless
- wouldn't it be easier to use w_scan output to configure tvtime app too? why me-tv app can do it while tvtime wants output from tvtime-scanner?

thanks; cheers; on the 20th back.

- as far as 'couldn't open device' - maybe the os having anything to do ? ' just thinking; 16.04 me-tv just worked.

Can you help with this problem?

Provide an answer of your own, or ask peter b for more information if necessary.

To post a message you must log in.