Opened 12 years ago
Closed 12 years ago
#11225 closed Bug Report - General (Invalid)
Cannot start LiveTV in 0.26-fixes, but scheduled recordings work perfectly
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | unknown |
Component: | MythTV - General | Version: | 0.26-fixes |
Severity: | high | Keywords: | livetv |
Cc: | Ticket locked: | no |
Description
LiveTV used to work fine, but in the most recent version something happened that prevents it from starting. Nothing wrong with my HDPVR setup because scheduled recordings always start without a problem. It looks like there is only 7s to startup livetv - maybe this needs to be extended (I set the change time to 20s in mythtv-setup).
mythbackend --version Please attach all output as a file in bug reports. MythTV Version : v0.26.0-28-ge3087dd MythTV Branch : fixes/0.26 Network Protocol : 75 Library API : 0.26.20120822-1 QT Version : 4.8.3 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_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2 uname -a Linux mythbox 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Attachments (4)
Change History (6)
Changed 12 years ago by
Attachment: | mythbackend_cant_start_livetv_gdb.txt added |
---|
Changed 12 years ago by
Attachment: | mythbackend.20121107002139.8470.log added |
---|
mythbackend log file with -v all option
comment:1 Changed 12 years ago by
Please close the ticket - this appears to be the result of the remote frontend being incorrectly setup as a "secondary backend" in the mythbuntu control center. Once I removed mythbackend from the frontend, the problem went away.
comment:2 Changed 12 years ago by
Resolution: | → Invalid |
---|---|
Status: | new → closed |
Closing at request of ticket reporter
gdb output