vdr March 2008

vdr@linuxtv.org

108 participants
108 discussions

iptv EXT channels.conf format
by Simon Baxter 26 Mar '08

26 Mar '08

Hi I can only get one EXT source working. This is what my channels.conf looks like: NasaTV Public;IPTV:1:IPTV|S0P0|EXT|iptvstream.sh|1:P:0:2:3:0:0:1:0:0:0 NasaTV Media;IPTV:2:IPTV|S0P0|EXT|iptvstream.sh|1:P:0:2:3:0:0:1:0:0:0 NasaTV Education;IPTV:3:IPTV|S0P0|EXT|iptvstream.sh|1:P:0:2:3:0:0:1:0:0:0 Shine TV NZ;IPTV:4:IPTV|S0P0|EXT|iptvstream.sh|1:P:0:2:3:0:0:1:0:0:0 ROMA UNO;IPTV:5:IPTV|S0P0|EXT|iptvstream.sh|1:P:0:2:3:0:0:1:0:0:0 The corresponding unique numbers relate to the various URLs in … [View More]

4 8

wrong characters in EPG (vdr-1.5.18)
by Éric Laly 26 Mar '08

26 Mar '08

Hello all, I've rebuilt my vdr with two DVB-T cards. Until then it was running with a very old vdr (1.3) and DVB-S. My locale was set to fr_FR in order to have the good charset and everything was fine (vdr menu and EPG in french). With the new 1.5 series I've understood that vdr now supports unicode (since 1.5.12 ?) so my locale is now set to fr_FR.UTF-8. The vdr menus are in french and the accentuated character are good ( é, è, î, à ...) but in the EPG the accentuated characters are wrong … [View More]

4 13

Setup/OSD
by Guy Roussin 25 Mar '08

25 Mar '08

Hi, After i pressed Setup/OSD, i need to wait about 6 or 7 seconds before i get the menu/page. I try to change the language, truetype fonts but no effect. This is the only sub-menu with this problem. How can i track this bug ? I use vdr-1.5.17 from e-tobi on debian sarge. I've another vdr with the same config but the screen is quickly display when i press Setup/OSD Thanks, -- Guy Roussin

2 3

segmentation fault in vdr-sxfe
by Oliver Joa 25 Mar '08

25 Mar '08

hi, i use vdr-sxfe as a client for vdr with the xineliboutput-plugin. since i upgraded my debian system (testing), i always get a segmentation-fault when pressing a key. i start like this: vdr-sxfe --video sdl "xvdr:tcp://video4:37890" i can see the actual tv-program but when i press any key to switch to a other program or show the menu i get a segmentation fault. if i telnet to the server to the control-port and use the command "hitk m" or "hitk up/down" i can switch program an see the … [View More]

1 0

Autosort plugin segmentation fault
by Seppo Ingalsuo 25 Mar '08

25 Mar '08

Hi, Anyone using autosort? I recently updated autosort 0.0.10 to 0.1.3 because 0.0.10 could not handle large sorting jobs without getting interrupted by some kind of watchdog/timeout and vdr restart (even with -w 0). With 0.1.3 I get this about once per hour. Core was generated by `vdr -c/etc/vdr -E/etc/vdr -v/opt/vdr -L/usr/local/lib/vdr -Pxineliboutput --loc'. Program terminated with signal 11, Segmentation fault. #0 0xb7c2036a in free () from /lib/i686/cmov/libc.so.6 (gdb) where #0 … [View More]

2 2

[ANNOUNCE] VDR version 1.6.0 released
by Klaus Schmidinger 24 Mar '08

24 Mar '08

VDR version 1.6.0 is now available at ftp://ftp.cadsoft.de/vdr/vdr-1.6.0.tar.bz2 A summary of all the major changes since the last stable version 1.4.7 can be found at http://www.cadsoft.de/vdr/changelog.htm A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.18-1.6.0.diff When updating from version 1.4.7 please make sure you read the INSTALL and MANUAL files that come with the VDR source _before_ doing so! Please make … [View More]

4 4

[ANNOUNCE] vdr-actuator-1.1.1 plugin
by Luca Olivetti 23 Mar '08

23 Mar '08

Hello, I'm releasing version 1.1.1 of the "actuator" plugin available at http://www.ventoso.org/luca/vdr/ This plugin controls a linear actuator (or an horizon to horizon one) through the parallel port with a simple circuit. The actual changes were made for vdr-1.5.11 but I forgot to release it, so I'm releasing it now that vdr has reached 1.6.0. The changes: - Changes in SetPids call to adapt to vdr >= 1.5.11 - Added -Wno-parentheses to compiler options there are also some … [View More]

1 0

VDR 1.5.18 segfaults at startup on Debian Sarge
by Walter Meier 23 Mar '08

23 Mar '08

Hi List, I want to upgrade to 1.5.18, but it failed to start and I have no idea why? 1.4.7 did work fine for me. It seems to me that something is wrong with my fonts? Maybe someone can help me to find the right way? (gdb) run -l 3.0 -E /tmp/epgtest.data -v /usr/local/src/vdr/vdr-1.5.17/video -c /usr/local/vdr/etc_1.6 Starting program: /daten/src/vdr/vdr-1.5.17/vdr -l 3.0 -E /tmp/epgtest.data -v /usr/local/src/vdr/vdr-1.5.17/video -c /usr/local/vdr/etc_1.6 [Thread debugging using … [View More]libthread_db enabled] [New Thread -1212243840 (LWP 13138)] [New Thread -1213690960 (LWP 13141)] [Thread -1213690960 (LWP 13141) exited] [New Thread -1222083664 (LWP 13142)] [Thread -1222083664 (LWP 13142) exited] [New Thread -1230476368 (LWP 13144)] [New Thread -1213690960 (LWP 13145)] [New Thread -1222083664 (LWP 13147)] [New Thread -1238869072 (LWP 13148)] [New Thread -1247261776 (LWP 13149)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1212243840 (LWP 13138)] 0xb7c90d04 in mallopt () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt #0 0xb7c90d04 in mallopt () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7c9150a in mallopt () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7c90135 in realloc () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7e48a16 in FcCharSetDestroy () from /usr/lib/libfontconfig.so.1 #4 0xb7e48b5c in FcCharSetFindLeafCreate () from /usr/lib/libfontconfig.so.1 #5 0xb7e4a067 in FcNameParseCharSet () from /usr/lib/libfontconfig.so.1 #6 0xb7e5253a in FcNameBool () from /usr/lib/libfontconfig.so.1 #7 0xb7e52783 in FcNameParse () from /usr/lib/libfontconfig.so.1 #8 0xb7e43ef6 in FcBlanksIsMember () from /usr/lib/libfontconfig.so.1 #9 0xb7e44649 in FcGlobalCacheScanDir () from /usr/lib/libfontconfig.so.1 #10 0xb7e4b568 in FcDirScanConfig () from /usr/lib/libfontconfig.so.1 #11 0xb7e45f8a in FcConfigBuildFonts () from /usr/lib/libfontconfig.so.1 #12 0xb7e4e8fc in FcInitLoadConfigAndFonts () from /usr/lib/libfontconfig.so.1 #13 0xb7e4e955 in FcInit () from /usr/lib/libfontconfig.so.1 #14 0x080bc39c in cFont::GetFontFileName (FontName=0xb7e66828 "4�\002") at font.c:411 #15 0x080bc083 in cFont::CreateFont (Name=0x8b5fb252 <Address 0x8b5fb252 out of bounds>, CharHeight=-1956662702, CharWidth=-1956662702) at font.c:356 #16 0x080bbf29 in cFont::SetFont (Font=fontOsd, Name=0x8b5fb252 <Address 0x8b5fb252 out of bounds>, CharHeight=-1956662702) at font.c:331 #17 0x080bc00d in cFont::GetFont (Font=136654904) at font.c:346 #18 0x081064c5 in cSkinSTTNGDisplayChannel (this=0x82502d8) at skinsttng.c:157 #19 0x0810e99d in cSkinSTTNG::DisplayChannel (this=0x824de60, WithInfo=true) at skinsttng.c:1157 #20 0x080d2e3f in cDisplayChannel (this=0x824c548, Number=-1956662702, Switched=true) at skins.h:327 #21 0x081244be in main (argc=1, argv=0xbfe873b4) at device.h:253 Bye, Walter [View Less]

1 1

vdr-dvd-cvs: deadlock when switching audio channel
by Reinhard Nissl 23 Mar '08

23 Mar '08

Hi, please have a look at the backtraces of the following threads: VDR's main thread: > (gdb) bt > #0 0xffffe410 in __kernel_vsyscall () > #1 0xb7f20c1e in __lll_mutex_lock_wait () from /lib/libpthread.so.0 > #2 0xb7f1ca58 in _L_mutex_lock_86 () from /lib/libpthread.so.0 > #3 0xb7f1c47d in __pthread_mutex_lock (mutex=0xa44ceec) at pthread_mutex_lock.c:81 > #4 0x0814e111 in cMutex::Lock (this=0xa44ceec) at thread.c:191 > #5 0x080c0656 in cThread::Lock (this=… [View More]0xa44cedc) at thread.h:91 > #6 0x0814e14a in cThreadLock::Lock (this=0xbfbeea90, Thread=0xa44cedc) at thread.c:392 > #7 0x0814e18e in cThreadLock (this=0xbfbeea90, Thread=0xa44cedc) at thread.c:379 > #8 0xb7a9e6d4 in cDvdPlayer::SetAudioTrack (this=0xa44ced0, Type=ttDolby, TrackId=0xa3d1a62) at player-dvd.c:2536 > #9 0x080bb367 in cDevice::SetCurrentAudioTrack (this=0xa3d11a0, Type=ttDolby) at device.c:1058 > #10 0x080e88d9 in cDisplayTracks::ProcessKey (this=0x88021d8, Key=kAudio) at menu.c:3595 > #11 0x080e3773 in cDisplayTracks::Process (Key=kAudio) at menu.c:3545 > #12 0x0815dec5 in main (argc=16, argv=0xbfbeef34) at vdr.c:1035 vdr-dvd's DvdPlayer thread: > (gdb) bt > #0 0x08159ef8 in Watchdog (signum=14) at vdr.c:164 > #1 <signal handler called> > #2 0xffffe40e in __kernel_vsyscall () > #3 0xb7f20c1e in __lll_mutex_lock_wait () from /lib/libpthread.so.0 > #4 0xb7f1ca58 in _L_mutex_lock_86 () from /lib/libpthread.so.0 > #5 0xb7f1c47d in __pthread_mutex_lock (mutex=0xa3d224c) at pthread_mutex_lock.c:81 > #6 0x0814e111 in cMutex::Lock (this=0xa3d224c) at thread.c:191 > #7 0x0814e1e2 in cMutexLock::Lock (this=0xb18f61a0, Mutex=0xa3d224c) at thread.c:366 > #8 0x0814e226 in cMutexLock (this=0xb18f61a0, Mutex=0xa3d224c) at thread.c:353 > #9 0x080bf264 in cDevice::PlayPesPacket (this=0xa3d11a0, Data=0xafd00690 "", Length=2034, VideoOnly=false) at device.c:1274 > #10 0x080be564 in cDevice::PlayPes (this=0xa3d11a0, Data=0xafd00690 "", Length=2034, VideoOnly=false) at device.c:1410 > #11 0x081141f3 in cPlayer::PlayPes (this=0xa44ced0, Data=0xafd00690 "", Length=2034, VideoOnly=false) at player.c:29 > #12 0xb7a9fdf1 in cDvdPlayer::Action (this=0xa44ced0) at player-dvd.c:730 > #13 0x0814de6e in cThread::StartThread (Thread=0xa44cedc) at thread.c:255 > #14 0xb7f1a192 in start_thread (arg=0xb18f6b90) at pthread_create.c:296 > #15 0xb7cd902e in clone () from /lib/libc.so.6 In frame #9 of VDR's main thread, mutexCurrentAudioTrack get's locked, then in frame #8, cDvbPlayer's thread mutex is to be aquired (LOCK_THREAD). In frame #12 vdr-dvd's DvdPlayer thread locked it's mutex (LOCK_THREAD), then in frame #9, mutexCurrentAudioTrack is to be aquired. As both threads lock the same mutexes in opposite order a deadlock occurs. As I'm not used to vdr-dvd development, I would be glad if someone could provide a fix for this issue. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de [View Less]

1 0

Re: [vdr] [ANNOUNCE] vdr-sudoku-0.2.0
by Ville Skyttä 23 Mar '08

23 Mar '08

On Saturday 22 March 2008, Thomas Günther wrote: > Ville Skyttä wrote: > > > - no-exit: Remove the "Exit" choice from the commands menu; exiting the > > plugin using this menu entry exits the plugin fine but next time any VDR > > OSD should appear after doing this, VDR crashes (VDR 1.4.7, Fedora Core > > 8). This is obviously just a stopgap patch, it'd be better if this could > > be fixed properly. > > Sorry, this was a last minute change, without … [View More]

1 0

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2008