Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: Does mythbackend prevent MeTV program from working?

  1. #1
    Join Date
    Dec 2006
    Beans
    Hidden!

    Does mythbackend prevent MeTV program from working?

    MeTV when I start it gives me a warning failed to get frontend.

    I think the backend is hogging my tuner card?
    Attached Images Attached Images

  2. #2
    Join Date
    Nov 2013
    Beans
    112

    Re: Does mythbackend prevent MeTV program from working?

    Quote Originally Posted by sdowney717 View Post
    MeTV when I start it gives me a warning failed to get frontend.

    I think the backend is hogging my tuner card?
    In the backend setup is the DVB tuner card set up with the option "open DVB tuner on demand"? If this is left unchecked, mythbackend doesn't free the tuner for other programs.

  3. #3
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: Does mythbackend prevent MeTV program from working?

    I went back and looked and do not see it.
    Where exactly is that in the backend?

    You can get backend to run smaller by setting the size, so now I can take screen shots.
    Attached Images Attached Images

  4. #4
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: Does mythbackend prevent MeTV program from working?

    I found it under recording options on that page.

    I have some kind of new error as you can see on the picture.
    MeTv also shows same error and cant watch TV

    MythTV shows that error in backend setup, but CAN watch TV.

    Any ideas? Reboot?

  5. #5
    Join Date
    Nov 2013
    Beans
    112

    Re: Does mythbackend prevent MeTV program from working?

    If you suspect mythbackend is hogging the tuner card so that me-tv doesn't work, kill the mythbackend process from a terminal. If the me-tv viewer still can't access the card with mythbackend killed, then the issue is either with the me-tv program itself, or the driver load for the tuner card. Perhaps even something as simple-minded as me-tv running from your main user account with the wrong permissions to access or tune the card.

    Otherwise, check dmesg output for issues occurring when the driver loads at boot, as well as checking the mythbackend log (or enabling logging in mythbackend if it happens to be disabled) to find out what mythbackend thinks is happenning when it starts up, or when it tunes a channel. I don't use Me-TV, but it does not appear to be to have logging or debugging of its own.

    You do not need to fuss around with sizing to deal with a combination both of full-screen mythtv-setup, mythfrontend, and other windowed applications. You can run mythbackend (sudo) from a desktop termininal, fullscreen mythtv-setup and/or mythfrontend also from desktop terminals, and then cheerily jump from app to app or desktop as necessary with alt-tab (in XFCE) or ctrl-esc (in KDE) or whatever the shortcut is in whatever environment you use.
    Last edited by aelfric55; April 2nd, 2014 at 01:21 PM.

  6. #6
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: Does mythbackend prevent MeTV program from working?

    I am running Trusty - beta

    Myth is till working, I can watch TV

    But I notice now this error in myth backend
    Also the error in Me-TV has changed to 'There are no DVB devices available'

    So now something is affecting both mythtv and metv

    Code:
    scott@scott-P5QC:~$ mythbackend
    2014-04-02 08:30:47.448891 C  mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
    2014-04-02 08:30:47.448909 C  Qt version: compile: 4.8.6, runtime: 4.8.6
    2014-04-02 08:30:47.448912 N  Enabled verbose msgs:  general
    2014-04-02 08:30:47.448921 N  Setting Log Level to LOG_INFO
    2014-04-02 08:30:47.459567 I  Added logging to the console
    2014-04-02 08:30:47.460200 I  Setup Interrupt handler
    2014-04-02 08:30:47.460215 I  Setup Terminated handler
    2014-04-02 08:30:47.460228 I  Setup Segmentation fault handler
    2014-04-02 08:30:47.460241 I  Setup Aborted handler
    2014-04-02 08:30:47.460253 I  Setup Bus error handler
    2014-04-02 08:30:47.460266 I  Setup Floating point exception handler
    2014-04-02 08:30:47.460279 I  Setup Illegal instruction handler
    2014-04-02 08:30:47.460294 I  Setup Real-time signal 0 handler
    2014-04-02 08:30:47.460338 N  Using runtime prefix = /usr
    2014-04-02 08:30:47.460354 N  Using configuration directory = /home/scott/.mythtv
    2014-04-02 08:30:47.460432 I  Assumed character encoding: en_US.UTF-8
    2014-04-02 08:30:47.460860 N  Empty LocalHostName.
    2014-04-02 08:30:47.460872 I  Using localhost value of scott-P5QC
    2014-04-02 08:30:47.501667 N  Setting QT default locale to EN_US
    2014-04-02 08:30:47.501724 I  Current locale EN_US
    2014-04-02 08:30:47.501769 N  Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
    2014-04-02 08:30:47.506550 I  Current MythTV Schema Version (DBSchemaVer): 1317
    2014-04-02 08:30:47.506855 I  Loading en_us translation for module mythfrontend
    2014-04-02 08:30:47.507208 N  MythBackend: Starting up as the master server.
    2014-04-02 08:30:47.509038 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.559135 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.561722 I  New Client:  (#1)
    2014-04-02 08:30:47.609300 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.659442 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.709602 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.759702 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.809853 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.859994 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.910150 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:47.960275 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.010433 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.060565 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.110722 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.160822 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.210973 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.261113 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.311268 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.361376 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.411526 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.461657 W  DVBChan[1](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.461671 E  DVBChan[1](/dev/dvb/adapter0/frontend0): Failed to open DVB frontend device due to fatal error or too many attempts.
    2014-04-02 08:30:48.461691 E  ChannelBase: CreateChannel() Error: Failed to open device /dev/dvb/adapter0/frontend0
    2014-04-02 08:30:48.461773 E  Problem with capture cardsCard 1failed init
    2014-04-02 08:30:48.462687 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.512844 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.562944 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.613099 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.663201 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.713350 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.763447 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.813600 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.863750 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.913908 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:48.964036 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.014190 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.064316 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.114473 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.164574 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.214731 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.264847 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.315004 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.365115 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.415268 W  DVBChan[2](/dev/dvb/adapter0/frontend0): Opening DVB frontend device failed.
    			eno: Device or resource busy (16)
    2014-04-02 08:30:49.415284 E  DVBChan[2](/dev/dvb/adapter0/frontend0): Failed to open DVB frontend device due to fatal error or too many attempts.
    2014-04-02 08:30:49.415294 E  ChannelBase: CreateChannel() Error: Failed to open device /dev/dvb/adapter0/frontend0
    2014-04-02 08:30:49.415332 E  Problem with capture cardsCard 2failed init
    2014-04-02 08:30:49.415355 W  MythBackend: No valid capture cards are defined in the database.
    2014-04-02 08:30:49.416236 W  Scheduler: Listings source '' is defined, but is not attached to a card input.
    2014-04-02 08:30:49.417728 I  Found 0 distinct programid authorities
    2014-04-02 08:30:49.418035 I  Registering HouseKeeperTask 'LogClean'.
    2014-04-02 08:30:49.418148 I  Registering HouseKeeperTask 'DBCleanup'.
    2014-04-02 08:30:49.418176 I  Registering HouseKeeperTask 'ThemeUpdateNotifications'.
    2014-04-02 08:30:49.418209 I  Registering HouseKeeperTask 'RecordedArtworkUpdate'.
    2014-04-02 08:30:49.418414 I  New static DB connectionSchedCon
    2014-04-02 08:30:49.420880 I  Registering HouseKeeperTask 'MythFillDB'.
    2014-04-02 08:30:49.420913 I  Registering HouseKeeperTask 'JobQueueRecover'.
    2014-04-02 08:30:49.420931 I  Registering HouseKeeperTask 'HardwareProfiler'.
    2014-04-02 08:30:49.422936 I  Starting HouseKeeper.
    2014-04-02 08:30:49.428087 E  Failed listening on TCP 127.0.0.1:6544 - Error 8: The bound address is already in use
    2014-04-02 08:30:49.428126 E  MediaServer::HttpServer Create Error
    2014-04-02 08:30:49.430812 E  Failed listening on TCP 127.0.0.1:6543 - Error 8: The bound address is already in use
    2014-04-02 08:30:49.430836 C  Backend exiting, MainServer initialization error.
    scott@scott-P5QC:~$
    Attached Images Attached Images

  7. #7
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: Does mythbackend prevent MeTV program from working?

    mythfrontend can watch TV even with that mythbackend error?


    Code:
    scott@scott-P5QC:~$ mythfrontend -w --geometry 1024x768
    2014-04-02 08:39:00.059438 I  Setup Interrupt handler
    2014-04-02 08:39:00.059463 I  Setup Terminated handler
    2014-04-02 08:39:00.059470 I  Setup Segmentation fault handler
    2014-04-02 08:39:00.059477 I  Setup Aborted handler
    2014-04-02 08:39:00.059483 I  Setup Bus error handler
    2014-04-02 08:39:00.059491 I  Setup Floating point exception handler
    2014-04-02 08:39:00.059498 I  Setup Illegal instruction handler
    2014-04-02 08:39:00.059506 I  Setup Real-time signal 0 handler
    2014-04-02 08:39:00.059515 I  Setup User defined signal 1 handler
    2014-04-02 08:39:00.059521 I  Setup User defined signal 2 handler
    2014-04-02 08:39:00.059620 C  mythfrontend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
    2014-04-02 08:39:00.059625 C  Qt version: compile: 4.8.6, runtime: 4.8.6
    2014-04-02 08:39:00.059628 N  Enabled verbose msgs:  general
    2014-04-02 08:39:00.059638 N  Setting Log Level to LOG_INFO
    2014-04-02 08:39:00.070324 I  Added logging to the console
    2014-04-02 08:39:00.070445 I  MythUIHelper: Overriding GUI size: width=1024 height=768
    2014-04-02 08:39:00.070496 N  Using runtime prefix = /usr
    2014-04-02 08:39:00.070509 N  Using configuration directory = /home/scott/.mythtv
    2014-04-02 08:39:00.070587 I  Assumed character encoding: en_US.UTF-8
    2014-04-02 08:39:00.071121 N  Empty LocalHostName.
    2014-04-02 08:39:00.071132 I  Using localhost value of scott-P5QC
    2014-04-02 08:39:00.082249 N  Setting QT default locale to EN_US
    2014-04-02 08:39:00.082321 I  Current locale EN_US
    2014-04-02 08:39:00.082418 N  Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
    2014-04-02 08:39:00.084894 I  Starting process manager
    2014-04-02 08:39:00.087333 I  Starting process signal handler
    2014-04-02 08:39:00.087422 I  Starting IO manager (write)
    2014-04-02 08:39:00.087507 I  Starting IO manager (read)
    2014-04-02 08:39:00.171540 I  New Client:  (#1)
    2014-04-02 08:39:00.171578 I  Added syslogging
    2014-04-02 08:39:00.188913 I  ScreenSaverX11Private: DPMS is active.
    2014-04-02 08:39:00.202391 N  Desktop video mode: 1680x1050 59.883 Hz
    2014-04-02 08:39:00.385333 N  Setting 'RunFrontendInWindow' being forced to '1'
    2014-04-02 08:39:00.387985 I  Listening on TCP 127.0.0.1:6547
    2014-04-02 08:39:00.388049 I  Listening on TCP [::1]:6547
    2014-04-02 08:39:00.388136 I  Listening on TCP [fe80::222:15ff:fe54:faa6%eth1]:6547
    Got bus address:  "unix:abstract=/tmp/dbus-AxBkNHUlkj,guid=dd0e4e814444ecf64ef4ca3f533bf45c" 
    Connected to accessibility bus at:  "unix:abstract=/tmp/dbus-AxBkNHUlkj,guid=dd0e4e814444ecf64ef4ca3f533bf45c" 
    Registered DEC:  true 
    2014-04-02 08:39:01.089494 I  Connecting to lcd server: 127.0.0.1:6545 (try 1 of 10)
    2014-04-02 08:39:01.090160 I  Loading en_us translation for module mythfrontend
    2014-04-02 08:39:01.090543 W  MythUIHelper: No theme dir: '/usr/share/mythtv/themes/Mythbuntu'
    2014-04-02 08:39:01.090563 E  MythUIHelper: Could not find theme: Mythbuntu - Switching to Terra
    2014-04-02 08:39:01.097104 E  LIRC: Failed to connect to Unix socket '/dev/lircd'
    			eno: No such file or directory (2)
    2014-04-02 08:39:01.097162 E  JoystickMenuThread: Joystick disabled - Failed to read /home/scott/.mythtv/joystickmenurc
    2014-04-02 08:39:01.097175 I  UDPListener: Enabling
    2014-04-02 08:39:01.097741 I  Binding to UDP 127.0.0.1:6948
    2014-04-02 08:39:01.097844 I  Binding to UDP [::1]:6948
    2014-04-02 08:39:01.097944 I  Binding to UDP [fe80::222:15ff:fe54:faa6%eth1]:6948
    2014-04-02 08:39:01.134847 I  Using the Qt painter
    2014-04-02 08:39:01.288742 I  MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
    2014-04-02 08:39:01.289740 I  Using protocol version 77
    2014-04-02 08:39:01.508329 I  MythUIWebBrowser: Loading css from - file:///usr/share/mythtv/themes/default/htmls/mythbrowser.css
    2014-04-02 08:39:01.508807 E  MythUIWebBrowser: failed to find our parent screen
    2014-04-02 08:39:01.509800 I  MythUIWebBrowser: enabling plugins
    2014-04-02 08:39:01.539840 E  RAOP Device: Aborting startup - no key found.
    2014-04-02 08:39:01.540206 I  AirPlay: Created airplay objects.
    2014-04-02 08:39:01.541438 I  Current MythTV Schema Version (DBSchemaVer): 1317
    2014-04-02 08:39:01.543109 I  Listening on TCP 127.0.0.1:5100
    2014-04-02 08:39:01.543184 I  Listening on TCP [::1]:5100
    2014-04-02 08:39:01.543250 I  Listening on TCP [fe80::222:15ff:fe54:faa6%eth1]:5100
    2014-04-02 08:39:01.565046 W  ThemeInfo: Unable to open themeinfo.xml for /usr/share/mythtv/themes/BlackCurves-OSD/themeinfo.xml
    2014-04-02 08:39:01.565057 E  ThemeInfo: The theme (/usr/share/mythtv/themes/BlackCurves-OSD) is missing a themeinfo.xml file.
    2014-04-02 08:39:01.565497 W  ThemeInfo: Unable to open themeinfo.xml for /usr/share/mythtv/themes/Gray-OSD/themeinfo.xml
    2014-04-02 08:39:01.565503 E  ThemeInfo: The theme (/usr/share/mythtv/themes/Gray-OSD) is missing a themeinfo.xml file.
    2014-04-02 08:39:01.645678 N  Registering Internal as a media playback plugin.
    2014-04-02 08:39:01.666645 W  No plugins directory /usr/lib/mythtv/plugins
    Registered event listener change listener:  true 
    2014-04-02 08:39:01.744041 N  Found mainmenu.xml for theme 'Terra'
    2014-04-02 08:39:01.746333 I  Registering HouseKeeperTask 'HardwareProfiler'.
    2014-04-02 08:39:01.746950 I  Starting HouseKeeper.
    2014-04-02 08:39:01.968037 I  Bonjour: Service registration complete: name 'Mythfrontend on scott-P5QC' type '_mythfrontend._tcp.' domain: 'local.'
    2014-04-02 08:39:02.519761 I  Bonjour: Service registration complete: name 'MythTV on scott-P5QC' type '_airplay._tcp.' domain: 'local.'
    2014-04-02 08:39:04.254780 I  TV: Creating TV object
    2014-04-02 08:39:04.263317 N  Suspending idle timer
    2014-04-02 08:39:04.267742 I  TV: Created TvPlayWindow.
    2014-04-02 08:39:04.288874 I  TV: Attempting to change from None to WatchingLiveTV
    2014-04-02 08:39:04.289711 I  MythCoreContext: Connecting to backend server: ::1:6543 (try 1 of 1)
    2014-04-02 08:39:04.296056 N  TV: Spawning LiveTV Recorder -- begin
    2014-04-02 08:39:04.373795 N  TV: Spawning LiveTV Recorder -- end
    2014-04-02 08:39:04.375988 I  TV: playbackURL(/var/lib/mythtv/recordings/2101_20140402123904.mpg) cardtype(DUMMY)
    greedyhdeint: size changed from 0 x 0 -> 720 x 576
    2014-04-02 08:39:04.420772 E  ALSA: snd_pcm_info_get_card: Operation not permitted
    2014-04-02 08:39:04.439209 N  AudioPlayer: Enabling Audio
    2014-04-02 08:39:04.453484 I  Setup Interrupt handler
    2014-04-02 08:39:04.453493 I  Setup Terminated handler
    2014-04-02 08:39:04.453576 I  VideoOutputXv: XVideo Adaptor Name: 'NV17 Video Texture'
    2014-04-02 08:39:04.470328 I  OSD: Base theme size: 1280x720
    2014-04-02 08:39:04.470349 I  OSD: Scaling factors: 0.5625x0.8
    2014-04-02 08:39:04.513239 I  OSD: Base theme size: 1280x720
    2014-04-02 08:39:04.513251 I  OSD: Scaling factors: 0.5625x0.8
    2014-04-02 08:39:04.518018 I  Player(0): Video timing method: USleep with busy wait
    2014-04-02 08:39:04.518626 I  TV: Created player.
    2014-04-02 08:39:04.518658 I  TV: Changing from None to WatchingLiveTV
    2014-04-02 08:39:04.518665 I  TV: State is LiveTV & mctx == ctx
    2014-04-02 08:39:04.519373 I  TV: UpdateOSDInput done
    2014-04-02 08:39:04.519381 I  TV: UpdateLCD done
    2014-04-02 08:39:04.519499 I  TV: ITVRestart done
    2014-04-02 08:39:04.523002 I  TV: Main UI disabled.
    2014-04-02 08:39:04.523031 I  TV: Entering main playback loop.
    2014-04-02 08:39:04.530577 I  ScreenSaverX11Private: DPMS Deactivated 1
    2014-04-02 08:39:04.584647 I  VideoOutput: Created YV12 OSD.
    2014-04-02 08:39:04.901861 E  Failed to mount /dev/sr0.
    2014-04-02 08:39:06.283489 I  AFD: codec AC3 has 6 channels
    2014-04-02 08:39:06.283741 I  AFD: Opened codec 0x360b8c0, id(AC3) type(Audio)
    2014-04-02 08:39:06.283930 I  AFD: codec AC3 has 1 channels
    2014-04-02 08:39:06.284124 I  AFD: Opened codec 0x3764340, id(AC3) type(Audio)
    2014-04-02 08:39:06.287277 I  Setup Interrupt handler
    2014-04-02 08:39:06.287290 I  Setup Terminated handler
    2014-04-02 08:39:06.291581 I  Setup Interrupt handler
    2014-04-02 08:39:06.291593 I  Setup Terminated handler
    2014-04-02 08:39:06.291692 I  VideoOutputXv: XVideo Adaptor Name: 'NV17 Video Texture'
    2014-04-02 08:39:06.368401 I  OSD: Base theme size: 1280x720
    2014-04-02 08:39:06.368415 I  OSD: Scaling factors: 1.12422x1.5
    2014-04-02 08:39:06.410766 I  AFD: Opened codec 0x35de0a0, id(MPEG2VIDEO) type(Video)
    2014-04-02 08:39:06.410905 I  AOBase: Opening audio device 'default' ch 2(6) sr 48000 sf 32 bit floating point reenc 0
    2014-04-02 08:39:06.426396 E  ALSA: no playback control PCM found on mixer device default
    2014-04-02 08:39:06.426406 E  ALSA: Unable to open audio mixer. Volume control disabled
    2014-04-02 08:39:06.573859 I  VideoOutput: Created YV12 OSD.
    2014-04-02 08:39:07.082014 N  Player(0): Waited 102ms for video buffers AAAAAAAAAAAAAAAAAAAUUUUUUUUUUuLP
    2014-04-02 08:39:07.331176 N  Player(0): Waited 104ms for video buffers UUuUULuAAAAAAAAAAAAAAAAAAAUUUUUP
    2014-04-02 08:39:07.856878 N  Player(0): Waited 104ms for video buffers AAAAAAAAAAAUUUUUUuUULUuAAAAAAAAP

  8. #8
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: Does mythbackend prevent MeTV program from working?

    Quote Originally Posted by aelfric55 View Post
    If you suspect mythbackend is hogging the tuner card so that me-tv doesn't work, kill the mythbackend process from a terminal. If the me-tv viewer still can't access the card with mythbackend killed, then the issue is either with the me-tv program itself, or the driver load for the tuner card. Perhaps even something as simple-minded as me-tv running from your main user account with the wrong permissions to access or tune the card.

    Otherwise, check dmesg output for issues occurring when the driver loads at boot, as well as checking the mythbackend log (or enabling logging in mythbackend if it happens to be disabled) to find out what mythbackend thinks is happenning when it starts up, or when it tunes a channel. I don't use Me-TV, but it does not appear to be to have logging or debugging of its own.

    You do not need to fuss around with sizing to deal with a combination both of full-screen mythtv-setup, mythfrontend, and other windowed applications. You can run mythbackend (sudo) from a desktop termininal, fullscreen mythtv-setup and/or mythfrontend also from desktop terminals, and then cheerily jump from app to app or desktop as necessary with alt-tab (in XFCE) or ctrl-esc (in KDE) or whatever the shortcut is in whatever environment you use.
    yes, something has happened to permissions on the tuner!
    If I run 'sudo me-tv', it works fine.
    Not sure I did anything to permissions, all I did was configure mythtv.
    I found this as a clue in launchpad bugs, mentions

    And now I figured it out properly.

    The DVB adapters were in accessible by a special "video" group only. The MythTV daemon account was a member of this group.

    My interactive a/c that I was using to test MeTV wasn't.

    Either the MythTV setup did this itself, or I did it some ages ago and forgot about it.

    When I added the interactive a/c to the right group it works without sudo.

    My bug. Close as invalid.
    https://bugs.launchpad.net/me-tv/+bug/619530

    Does mythtv do something affecting groups, permissions?
    So what do i assign to what group to let me-tv work again without needing sudo?

  9. #9
    Join Date
    Nov 2013
    Beans
    112

    Re: Does mythbackend prevent MeTV program from working?

    Note that mythbackend runs with root permissions to access hardware ; if you start it from your user's regular terminal, it's done sudo after the already-running mythbackend (or in Ubuntu mythbackend.real) has been stopped This is the error problem in your first mythbackend screen dump, where it looks like mythbackend was run as your regular user.

    Since me-tv works when run sudo, that's its problem too --insufficient normal user account permissions. If such a "video" group exists on your machine, as mentioned by the poster on your launchpad excerpt, then this group must have root access to hardware if this is how mythbackend is running. If you intend to run me-tv always from your main user account and me-tv needs to access video hardware, then logically your main user's account will need to be added to the video group.

    If, however, mythbackend (or mythbackend.real) is simply running as root, without a "video" group to belong to, then you'll likely want to create such a group yourself, using the user/group tools provided by your desktop (generally easier than editing files in /etc). This "video" group will need to be given appropriate hardware access to be able to tune the card, and then your main user will need to be added to that group. Logout, log back in, and the main user (and therefore me-tv) should be able to access the tuner card.

  10. #10
    Join Date
    Nov 2006
    Location
    Oregon
    Beans
    4,427
    Distro
    Ubuntu Development Release

    Re: Does mythbackend prevent MeTV program from working?

    Quote Originally Posted by aelfric55 View Post
    If you suspect mythbackend is hogging the tuner card so that me-tv doesn't work, kill the mythbackend process from a terminal.

    No, don't do that. It's much better to stop the mythbackend process properly (eg. 'sudo service mythtv-backend stop'). If you kill the process, it should attempt to restart automatically.
    *Don't PM me directly for support, open a new thread
    *Looking for a MythTV quick start guide?

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •