[SOLVED] Problem returning to softhddevice from XBMC

jbjbjb · November 2, 2012 at 11:14 AM

Hi,

This week in yaVDR 0.5 I have experienced twice the same problem. When I go back from XBMC to vdr (softhddevice) the screen freezes (black or with yavdr logo) and I can not do anything with the remote till I reboot by mean a ssh conection.

The two times I had the problem vdr was recording one scheduled timer.

Syslog is:

Code

Nov  1 22:45:05 yaVDR05 vdr: [1075] closing SVDRP connection
Nov  1 22:45:05 yaVDR05 vdr: [1075] connect from 127.0.0.1, port 60301 - accepted
Nov  1 22:45:05 yaVDR05 vdr: [1075] timer 8 (19 1930-2220 'Formula Uno~Fórmula 1 - Clasificación: Gp Abu Dhabi') modified (active)
Nov  1 22:45:05 yaVDR05 vdr: [1075] closing SVDRP connection
Nov  1 22:45:05 yaVDR05 vdr: [1262] XVDR: Timers state changed (223)
Nov  1 22:45:05 yaVDR05 vdr: [1262] XVDR: Requesting clients to reload timers
Nov  1 22:45:05 yaVDR05 vdr: [1251] EPGSearch: search timer update finished
Nov  1 22:45:13 yaVDR05 vdr: [1075] timer 3 (34 1545-1825 'peliculas~PelisFinde~Multicine: Vidas robadas') set to event Sab 03.11.2012 16:00-17:45 'Multicine: Vidas robadas'
Nov  1 22:45:13 yaVDR05 vdr: [1075] timer 4 (34 1730-2010 'peliculas~PelisFinde~Multicine: El destino está escrito') set to event Sab 03.11.2012 17:45-19:30 'Multicine: El destino está escrito'
Nov  1 22:45:13 yaVDR05 vdr: [1075] timer 5 (34 1915-2140 'peliculas~PelisFinde~Multicine: La sustituta') set to event Sab 03.11.2012 19:30-21:00 'Multicine: La sustituta'
Nov  1 22:45:13 yaVDR05 vdr: [1075] timer 7 (3 1320-1520 'Formula Uno~Fórmula 1. Clasificación: GP Abu Dhabi') set to event Sab 03.11.2012 13:30-15:00 'Fórmula 1. Clasificación: GP Abu Dhabi'
Nov  1 22:45:13 yaVDR05 vdr: [1075] timer 8 (19 1930-2220 'Formula Uno~Fórmula 1 - Clasificación: Gp Abu Dhabi') set to event Sab 03.11.2012 19:45-21:15 'Fórmula 1 - Clasificación: Gp Abu Dhabi'
Nov  1 22:45:20 yaVDR05 vdr: [1262] XVDR: Checking for channel updates ...
Nov  1 22:45:20 yaVDR05 vdr: [1262] XVDR: Client 0: 79 channels, no change
Nov  1 22:45:20 yaVDR05 vdr: [1262] XVDR: Done
******************************************************************************************************
Nov  1 22:45:34 yaVDR05 vdr: [3523] XVDR-Error: cxSocket::read: read() error at 0/4
******************************************************************************************************
Nov  1 22:45:34 yaVDR05 vdr: [1262] XVDR: Client with ID 0 seems to be disconnected, removing from client list
Nov  1 22:45:35 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable
Nov  1 22:45:35 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702cade0
Nov  1 22:45:35 yaVDR05 vdr: [3584] dbus2vdr message handler thread started (pid=1075, tid=3584)
Nov  1 22:45:35 yaVDR05 vdr: [3584] dbus2vdr: moving message handler 0x7f15702cade0 from active to finished
Nov  1 22:45:35 yaVDR05 vdr: [3584] dbus2vdr message handler thread ended (pid=1075, tid=3584)
Nov  1 22:45:35 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:45:35 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:45:36 yaVDR05 XBMC: XBMC exit with exit status , , ENV: TERM=linux#012PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin#012PWD=/#012JOB=xbmc#012RESULT=ok#012SHLVL=1#012HOME=/var/li$
Nov  1 22:45:36 yaVDR05 /usr/bin/signal-event.real[3591]: processing signal reset-display-rate
Nov  1 22:45:36 yaVDR05 /usr/bin/signal-event.real[3591]: processing action /usr/share/yavdr/events/reset-display-rate/10_reset-display-rate reset-display-rate
Nov  1 22:45:36 yaVDR05 /usr/bin/signal-event.real[3591]: finished processing signal reset-display-rate
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Plugins/softhddevice with Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Remote, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Remote with Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Shutdown with Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Setup, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Setup with Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ManualStart
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702cade0
Nov  1 22:45:37 yaVDR05 vdr: [3631] dbus2vdr message handler thread started (pid=1075, tid=3631)
Nov  1 22:45:37 yaVDR05 vdr: [3631] dbus2vdr: moving message handler 0x7f15702cade0 from active to finished
Nov  1 22:45:37 yaVDR05 vdr: [3631] dbus2vdr message handler thread ended (pid=1075, tid=3631)
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:45:37 yaVDR05 vdr-frontend[3627]: acip-wakeup.time.old hatte Wert: Thu Nov  1 05:15:00 2012
Nov  1 22:45:37 yaVDR05 vdr-frontend[3627]: vergleiche mit jetzt: Thu Nov  1 21:45:37 2012
Nov  1 22:45:37 yaVDR05 vdr-frontend[3627]: assuming manual start
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Plugins with Introspect
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: can't introspect object /Plugins
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins, interface de.tvdr.vdr.plugin, member List
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702cade0
Nov  1 22:45:37 yaVDR05 vdr: [3632] dbus2vdr message handler thread started (pid=1075, tid=3632)
Nov  1 22:45:37 yaVDR05 vdr: [3632] dbus2vdr: moving message handler 0x7f15702cade0 from active to finished
Nov  1 22:45:37 yaVDR05 vdr: [3632] dbus2vdr message handler thread ended (pid=1075, tid=3632)
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:45:37 yaVDR05 vdr-frontend[3627]: watching "MCE IR Keyboard/Mouse (nuvoton-cir)": /dev/input/event3
Nov  1 22:45:37 yaVDR05 vdr-frontend[3627]: started udev monitoring of input devices
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702cade0
Nov  1 22:45:37 yaVDR05 vdr: [3633] dbus2vdr message handler thread started (pid=1075, tid=3633)
Nov  1 22:45:37 yaVDR05 vdr: [3633] dbus2vdr: invoking softhddevice.SVDRPCommand("STAT", "None")
Nov  1 22:45:37 yaVDR05 vdr: [3633] dbus2vdr: moving message handler 0x7f15702cade0 from active to finished
Nov  1 22:45:37 yaVDR05 vdr: [3633] dbus2vdr message handler thread ended (pid=1075, tid=3633)
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:45:37 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702cade0
Nov  1 22:45:37 yaVDR05 vdr: [3635] dbus2vdr message handler thread started (pid=1075, tid=3635)
Nov  1 22:45:37 yaVDR05 vdr: [3635] dbus2vdr: invoking softhddevice.SVDRPCommand("ATTA", "-d :1.0")
Nov  1 22:45:37 yaVDR05 vdr: [3635] [softhddev]SetPlayMode: 0
Nov  1 22:45:37 yaVDR05 vdr: [3635] [softhddev]SetVideoDisplayFormat: 1
Nov  1 22:45:37 yaVDR05 vdr: [3635] [softhddev]~cSoftHdControl: dummy player stopped
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: VDPAU API version: 1
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: VDPAU information: NVIDIA VDPAU Driver Shared Library  304.51  Tue Sep 18 17:40:30 PDT 2012
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: highest supported high quality scaling 1
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: feature deinterlace temporal supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: feature deinterlace temporal spatial supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: attribute skip chroma deinterlace supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: 4:2:0 chroma format with 4096x4096 supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: 4:2:2 chroma format with 4096x4096 supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: 8bit BGRA format with 8192x8192 supported
Nov  1 22:45:37 yaVDR05 vdr: video/vdpau: 10bit RGBA format with 8192x8192 supported
Nov  1 22:45:37 yaVDR05 vdr: video: fatal i/o error
Nov  1 22:45:38 yaVDR05 vdr: [1075] switching to channel 4
Nov  1 22:45:38 yaVDR05 vdr: [3636] receiver on device 2 thread started (pid=1075, tid=3636)
Nov  1 22:45:38 yaVDR05 vdr: [3637] TS buffer on device 2 thread started (pid=1075, tid=3637)
Nov  1 22:45:39 yaVDR05 vdr: [1075] [softhddev]SetPlayMode: 1
Nov  1 22:45:52 yaVDR05 vdr: [3638] Text2Skin: channelInfo display update thread started (pid=1075, tid=3638)
Nov  1 22:45:56 yaVDR05 vdr: [3638] Text2Skin: channelInfo display update thread ended (pid=1075, tid=3638)
Nov  1 22:45:59 yaVDR05 vdr: [3641] Text2Skin: menu display update thread started (pid=1075, tid=3641)
Nov  1 22:46:00 yaVDR05 vdr: [3641] Text2Skin: menu display update thread ended (pid=1075, tid=3641)
Nov  1 22:46:02 yaVDR05 kernel: [59441.509068] init: vdr-frontend main process (3624) terminated with status 1
Nov  1 22:46:02 yaVDR05 kernel: [59441.509162] init: vdr-frontend main process ended, respawning
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: starting new message handler 0x7f15702c2be0
Nov  1 22:46:02 yaVDR05 vdr: [3649] dbus2vdr message handler thread started (pid=1075, tid=3649)
Nov  1 22:46:02 yaVDR05 vdr: [3649] dbus2vdr: de.tvdr.vdr.plugin.SVDRPCommand: command 'STAT' has no option
Nov  1 22:46:02 yaVDR05 vdr: [3649] dbus2vdr: invoking softhddevice.SVDRPCommand("STAT", "")
Nov  1 22:46:02 yaVDR05 vdr: [3649] dbus2vdr: moving message handler 0x7f15702c2be0 from active to finished
Nov  1 22:46:02 yaVDR05 vdr: [3649] dbus2vdr message handler thread ended (pid=1075, tid=3649)
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702c2be0
Nov  1 22:46:02 yaVDR05 vdr: [3652] dbus2vdr message handler thread started (pid=1075, tid=3652)
Nov  1 22:46:02 yaVDR05 vdr: [3652] dbus2vdr: de.tvdr.vdr.plugin.SVDRPCommand: command 'DETA' has no option
Nov  1 22:46:02 yaVDR05 vdr: [3652] dbus2vdr: invoking softhddevice.SVDRPCommand("DETA", "")
Nov  1 22:46:02 yaVDR05 vdr: [3652] dbus2vdr: moving message handler 0x7f15702c2be0 from active to finished
Nov  1 22:46:02 yaVDR05 vdr: [3652] dbus2vdr message handler thread ended (pid=1075, tid=3652)
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:46:02 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Plugins/softhddevice with Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Remote, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Remote with Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Shutdown with Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Setup, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Setup with Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ManualStart
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702c2be0
Nov  1 22:46:03 yaVDR05 vdr: [3674] dbus2vdr message handler thread started (pid=1075, tid=3674)
Nov  1 22:46:03 yaVDR05 vdr: [3674] dbus2vdr: moving message handler 0x7f15702c2be0 from active to finished
Nov  1 22:46:03 yaVDR05 vdr: [3674] dbus2vdr message handler thread ended (pid=1075, tid=3674)
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:46:03 yaVDR05 vdr-frontend[3670]: acip-wakeup.time.old hatte Wert: Thu Nov  1 05:15:00 2012
Nov  1 22:46:03 yaVDR05 vdr-frontend[3670]: vergleiche mit jetzt: Thu Nov  1 21:46:03 2012
Nov  1 22:46:03 yaVDR05 vdr-frontend[3670]: assuming manual start
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins, interface org.freedesktop.DBus.Introspectable, member Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: introspect object /Plugins with Introspect
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: can't introspect object /Plugins
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins, interface de.tvdr.vdr.plugin, member List
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702c2be0
Nov  1 22:46:03 yaVDR05 vdr: [3675] dbus2vdr message handler thread started (pid=1075, tid=3675)
Nov  1 22:46:03 yaVDR05 vdr: [3675] dbus2vdr: moving message handler 0x7f15702c2be0 from active to finished
Nov  1 22:46:03 yaVDR05 vdr: [3675] dbus2vdr message handler thread ended (pid=1075, tid=3675)
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:46:03 yaVDR05 vdr-frontend[3670]: watching "MCE IR Keyboard/Mouse (nuvoton-cir)": /dev/input/event3
Nov  1 22:46:03 yaVDR05 vdr-frontend[3670]: started udev monitoring of input devices
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702c2be0
Nov  1 22:46:03 yaVDR05 vdr: [3676] dbus2vdr message handler thread started (pid=1075, tid=3676)
Nov  1 22:46:03 yaVDR05 vdr: [3676] dbus2vdr: invoking softhddevice.SVDRPCommand("STAT", "None")
Nov  1 22:46:03 yaVDR05 vdr: [3676] dbus2vdr: moving message handler 0x7f15702c2be0 from active to finished
Nov  1 22:46:03 yaVDR05 vdr: [3676] dbus2vdr message handler thread ended (pid=1075, tid=3676)
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: connection has messages to send, flushing
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: done flushing
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Nov  1 22:46:03 yaVDR05 vdr: [1416] dbus2vdr: 1 idle message handler, reusing 0x7f15702c2be0
Nov  1 22:46:03 yaVDR05 vdr: [3678] dbus2vdr message handler thread started (pid=1075, tid=3678)
Nov  1 22:46:03 yaVDR05 vdr: [3678] dbus2vdr: invoking softhddevice.SVDRPCommand("ATTA", "-d :1.0")

Display More

Regards.
jbjbjb

seahawk1986 · November 2, 2012 at 11:47 AM

Quote from jbjbjb

Nov 1 22:46:02 yaVDR05 kernel: [59441.509068] init: vdr-frontend main process (3624) terminated with status 1
Nov 1 22:46:02 yaVDR05 kernel: [59441.509162] init: vdr-frontend main process ended, respawning

There seems to be a restart (probably caused by a Crash) of vdr-frontend - could you poste it's log /var/log/upstart/vdr-frontend.log ?

jbjbjb · November 2, 2012 at 11:59 AM

Hi.

Here you have the two last files. I hope the files are helpful to find out what happened.

Regards.
jbjbjb

johns · November 2, 2012 at 12:06 PM

The failure is:

Code

Nov  1 22:45:37 yaVDR05 vdr: video: fatal i/o error

there was a problem with the communication with X11.

X11 restarted?

Johns

jbjbjb · November 2, 2012 at 12:18 PM

Quote from johns
The failure is:
Code
Nov  1 22:45:37 yaVDR05 vdr: video: fatal i/o error
X11 restarted?

I am sorry but I do not know how to answer your question. The screen remained black till I rebooted by mean a ssh conection.

Regards.
jbjbjb

jbjbjb · November 4, 2012 at 9:34 AM

Hi.

Do you have find out what the problem is?

Any aditional info I can give?

Conecting by ssh and executing 'sudo restart vdr' does not work, what can I execute to recover interface?

Regards
jbjbjb

jbjbjb · November 5, 2012 at 6:25 PM

Hi.

The crash can be solved by mean ssh, executing "sudo restart vdr", but it takes more than one minute in recovering vdr again, that is the reason which I thought "restart vdr" did not work. I am not much patient.

The crash happens specially when there are an active recording, but not always.

Regards.
jbjbjb

Chucky · November 5, 2012 at 9:37 PM

Hello,

i had the some problem. In my case the following change to /usr/share/vdr/menuorg-appswitcher solved this problem for me

Code

*** menuorg-appswitcher	2012-11-05 21:33:33.320954383 +0100
--- /usr/share/vdr/menuorg-appswitcher	2012-10-30 20:49:15.291340315 +0100
***************
*** 27,33 ****

  # finished parsing arguments

! STOP="sudo /sbin/initctl stop --no-wait"

  # minimum required arguments
  if [ -z $STANDALONE ] || [ -z $APP ]; then
--- 27,34 ----

  # finished parsing arguments

! #STOP="sudo /sbin/initctl stop --no-wait"
! STOP="sudo /sbin/initctl stop"

  # minimum required arguments
  if [ -z $STANDALONE ] || [ -z $APP ]; then

Display More

With this change the system waits for the shutdown of the vdr-frontend before the program (xbmc) starts.

HTH

Chucky

jbjbjb · November 6, 2012 at 8:50 AM

Quote from Chucky

Hello,
i had the some problem. In my case the following change to /usr/share/vdr/menuorg-appswitcher solved this problem for me

Thanks, I will try it and I will let you know the results.

Regards.
jbjbjb

jbjbjb · November 7, 2012 at 8:55 AM

Hi.

Yesterday I tried the proprosed change about 15 times without problems, so, it seems to work also for me.

I have also modified the template "/usr/share/yavdr/templates/usr/share/vdr/menuorg-appswitcher/10_main" to avoid updates overwrite the file.

Thanks again.
Regards.
jbjbjb

DocViper · November 7, 2012 at 10:23 AM

I have added it to the bugtracker of yavdr so that other user will benefit from the solution soon automatically:

https://bugs.yavdr.com/issues/824

Thx
Joe

jbjbjb · November 7, 2012 at 10:54 AM

Thanks.

To keep intact the file after an update, I have copied the original template "/usr/share/yavdr/templates/usr/share/vdr/menuorg-appswitcher/10_main" in "/etc/yavdr/templates_custom/usr/share/vdr/menuorg-appswitcher/10_main" and I made the changes in this last file.

Regards.
jbjbjb

drops · November 7, 2012 at 7:11 PM

Hi Folks,

i got the same problem. Chucky did a great job. With this little correction it works perfect on my client.

Cheers

drops

DocViper · November 7, 2012 at 8:56 PM

It should be allready available when you update your yavdr 0.5 - thanks to Gerald fast build
And don't forget: For Yavdr always:

Code

sudo apt-get update
sudo apt-get dist-upgrade

jbjbjb · November 8, 2012 at 9:04 AM

Quote from DocViper
It should be allready available when you update your yavdr 0.5 - thanks to Gerald fast build
And don't forget: For Yavdr always:
Code
sudo apt-get update
sudo apt-get dist-upgrade

Updated!!.

Thanks for your great work.

Regards.
jbjbjb

[SOLVED] Problem returning to softhddevice from XBMC

Participate now!

Users Viewing This Thread