Mythtv-setup hangs in Capture Card

[rallan@…]

I have recently added a HDHomerun DUO to my configuration. However I cannot get mythtv-setup to get through the Capture Card process. This appears very similar to a previous bug report #12897 for which the error appeared to go away on its own accord.

The relevant part of the setup log appears to be:

2017-11-30 17:00:08.532770 D [1759/1759] CoreContext? recorders/vboxutils.cpp:89 (doUPNPSearch) - VBox: Found 2 possible VBoxes 2017-11-30 17:00:08.532859 D [1759/1759] CoreContext? recorders/vboxutils.cpp:114 (doUPNPSearch) - VBox: Found possible VBox at HDHomeRun DMS 10618811 (192.168.1.108:80) 2017-11-30 17:00:08.944212 I [1759/1759] CoreContext? recorders/vboxutils.cpp:106 (doUPNPSearch) - VBox: GetDeviceDesc?() failed for <Unknown> 2017-11-30 17:00:08.953479 E [1759/1759] CoreContext? v4l2util.cpp:58 (Open) - V4L2(): Could not open :

eno: No such file or directory (2)

2017-11-30 17:00:09.100094 W [1759/1759] CoreContext? diseqc.cpp:395 (Load) - DiSEqCDevTree: No device tree for cardid 17 2017-11-30 17:00:09.107486 W [1759/1759] CoreContext? diseqc.cpp:395 (Load) - DiSEqCDevTree: No device tree for cardid 17

The HDHomeRun has been correctly identified so communication must be possible. A database entry for the HDHomeRun has also been automatically generated in the table below:

select * from videosource; +----------+------------+------------------+--------+-----------+----------+----------+--------+------------+------------+ | sourceid | name | xmltvgrabber | userid | freqtable | lineupid | password | useeit | configpath | dvb_nit_id | +----------+------------+------------------+--------+-----------+----------+----------+--------+------------+------------+ | 1 | Tuner US | /bin/true | | us-bcast | NULL | NULL | 0 | NULL | -1 | | 3 | HD HomeRun? | schedulesdirect1 | | default | NULL | NULL | 0 | NULL | -1 | +----------+------------+------------------+--------+-----------+----------+----------+--------+------------+------------+

but no entry is generated in the CaptureCard? table. (N.B The previous card uses cardid 17 and 18).

I have waited 30 minutes (as suggested elsewhere) but still in a loop.

Is there any fix for this? or can someone suggest a fudge to modify database table entries to get round this impasse?

Version of mythtv-setup

MythTV Version : v29.0-59-g61d331c MythTV Branch : fixes/29 Network Protocol : 91 Library API : 29.20170212-1 QT Version : 5.3.2 Options compiled in: linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl using_qtwebkit using_qtscript using_qtdbus using_taglib using_v4l2 using_x11 using_xrandr using_xv using_profiletype using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_opengles using_openmax using_ffmpeg_threads using_mheg using_libass using_libxml2

I can provide additional details if required but cannot use the HDHomeRun at present.

Thank you for any assistance you can provide.

[rallan@…]

Further to my original post, I MAY not have understood how Capture Card is supposed to work. When a new card is created, it appears as a new entry at the end of the list of cards. This can be not visible (as it needs scrolling to) when pressing the new card request.

I have now managed to create the new HomeRun? card. However it should be noted (using remote X11 connection), the Rt-Arrow key is necessary to view the configuration sub menu. Pressing the mouse on the screen rt-arrow just brings up the menu of available tuners.

In conclusion, the bug as reported above, may be unjustified. However I still have problems with scheduling the HDHomeRuns which whilst working don't appear to be recognised by the scheduler

[Peter Bennett]

The new setup is designed to be used with keyboard or remote, not with the mouse. It works the same way as the frontend screens.