vdr December 2012

vdr@linuxtv.org

40 participants
44 discussions

Error reading channels.conf on sh4 platform
by Martin 03 Dec '12

03 Dec '12

Hi, I'm trying to get VDR working on my motorola Vip1900. VDR is running but it doesn't read the channels.conf Tried 1.7.29 & 1.7.27 both give the same problem. Tested with my own channels.conf and the channels.conf from the vdr-source. Any hints? /video # ls > channels.conf epg.data setup.conf themes > /video # vdr -L /vdr/lib -Pdummydevice -Pstreamdev-client > vdr: error while reading '/video/sources.conf' > vdr: error while reading '/video/channels.conf' syslog Dec 3 21:56:53 192 vdr: [1998] VDR version 1.7.27 started > Dec 3 21:56:53 192 vdr: [1998] codeset is 'ASCII' - unknown > Dec 3 21:56:53 192 vdr: [1998] ERROR (tools.c,1392): ./locale: No such > file or directory > Dec 3 21:56:53 192 vdr: [1998] no locale for language code 'deu,ger' > .... > Dec 3 21:56:53 192 vdr: [1998] loading plugin: > /vdr/lib/libvdr-dummydevice.so.1.7.27 > Dec 3 21:56:54 192 vdr: [1998] loading plugin: > /vdr/lib/libvdr-streamdev-client.so.1.7.27 > Dec 3 21:56:54 192 vdr: [1998] loading /video/setup.conf > Dec 3 21:56:54 192 vdr: [1998] loading /video/channels.conf > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 1 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 2 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 3 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 4 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 5 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 6 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 7 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 8 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 9 > Dec 3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line > 10

2 1

polarization character case in channels.conf
by Mike Hay 03 Dec '12

03 Dec '12

Hi list, I recently lost access to all vertically polarised channels and after quite a bit of floundering about I discovered the reason for this is due to the case of the polarisation character in channels.conf. According to the vdr changelog it has been possible to specify this in either upper or lower case since version 0.6 but it seems this is not correct - at least in 1.7.31. I generate my channels.conf with w_scan and it produces lower case "h" and "v" for polarisation. It seemed to work OK for the horizontal channels but not the vertical. Perhaps it works for horizontal because this is the default position... Anyway I have resolved my issue by manually changing the case of these characters in channels.conf but wondered if this is really a bug or just a misunderstanding on my part. Regards, Mike

4 8

get a segmentation fault when starting vdr (backtrace included)
by Dieter Bloms 02 Dec '12

02 Dec '12

Hello, I've compiled vdr on alpinelinux 2.5.0 and get a segfault during start of vdr. Even without plugins I get this segfault (I didn't apply any patch to vdr sources). Vdr was started with the command: /usr/local/bin/vdr --config=/etc/vdr --epgfile=/tmp/epg.data --grab=/dev/shm --log=3.1 --mute --no-kbd --user=root --video=/remote/vdr/ I've made a backtrace with gdb: --snip-- vdrservernew:/tmp# gdb --core core /usr/local/bin/vdr GNU gdb (GDB) 7.5 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/local/bin/vdr...done. [New LWP 26493] [New LWP 26492] [New LWP 26494] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `/usr/local/bin/vdr --config=/etc/vdr --epgfile=/tmp/epg.data --grab=/dev/shm --'. Program terminated with signal 11, Segmentation fault. #0 skipspace (s=0x40800000 <Address 0x40800000 out of bounds>) at tools.h:196 196 if ((uchar)*s > ' ') // most strings don't have any leading space, so handle this case as fast as possible (gdb) bt #0 skipspace (s=0x40800000 <Address 0x40800000 out of bounds>) at tools.h:196 #1 isempty (s=0x40800000 <Address 0x40800000 out of bounds>) at tools.c:249 #2 0x00000000004a1eb9 in FromString (s=0x2e531d2 "1 01 deu 4:3", this=0x2e4aba0) at epg.c:36 #3 cComponents::SetComponent (this=<optimized out>, Index=0, s=s@entry=0x2e531d2 "1 01 deu 4:3") at epg.c:81 #4 0x00000000004a40f3 in cEvent::Parse (this=0x2e43360, s=<optimized out>) at epg.c:495 #5 0x00000000004e9ea6 in cRecordingInfo::Read (this=0x2e2d110, f=f@entry=0x2e2c330) at recording.c:468 #6 0x00000000004eb4e3 in cRecording::cRecording (this=0x2e2c650, FileName=0x2e4c15c "Sex_and_the_City_2/2012-11-19.20.10.27-0.rec") at recording.c:723 #7 0x00000000004eceb1 in cRecordings::ScanVideoDir (this=0x7fe7c0 <Recordings>, DirName=0x2e412b0 "/remote/vdr/Sex_and_the_City_2", Foreground=false, LinkLevel=0) at recording.c:1165 #8 0x00000000004ed32c in cRecordings::ScanVideoDir (this=0x7fe7c0 <Recordings>, DirName=0x2e25ff0 "/remote/vdr", Foreground=false, LinkLevel=0) at recording.c:1180 #9 0x000000000052694e in cThread::StartThread (Thread=0x7fe7e0 <Recordings+32>) at thread.c:262 #10 0x00006e6b7ce69406 in start_thread () from /lib/libpthread.so.0.9.32 #11 0x00006e6b7ce61885 in clone () from /lib/libpthread.so.0.9.32 #12 0x0000000000000000 in ?? () --snip-- does anybody see what is wrong here ? -- Regards Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field.

8 17

[PATCH] small typo in skin.h
by Lars Hanisch 01 Dec '12

01 Dec '12

Hi, Just a small typo, for the sake of complete- and correctness... :) Lars.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2012