vdr always segfaults on start

[fishxz]

hey,
i started to use archlinux on my rpi server, cause i rly like it, but i cant get vdr to run. i tried both versions from aur and both give me a segfault error on startup. im running a pi with a sundtek usb stick. the same setup works flawless on rapsbian.

[hydro]

You could also try this package or this one. Setup is a bit different from AUR packages I guess, but it's explained on the site. I'd first try without any plugins.

[fishxz]

thanks, but i already tried this source with the same problem. i start a new try. i see there is a new version from today aviable.

$this->bbcode_second_pass_code('', 'Apr 16 14:39:06 alarmpi systemd[1]: Starting Video Disk Recorder...
Apr 16 14:39:06 alarmpi systemd[1]: Started Video Disk Recorder.
Apr 16 14:39:07 alarmpi runvdr[219]: vdr: no fonts available - OSD will not show any text!
Apr 16 14:39:09 alarmpi runvdr[219]: /usr/bin/runvdr: line 39: 221 Segmentation fault (core dumped) /usr/bin/vdr --lib=/usr/lib/vdr
Apr 16 14:39:09 alarmpi runvdr[219]: Tue Apr 16 14:39:08 BST 2013 reloading DVB driver
Apr 16 14:39:18 alarmpi runvdr[219]: Tue Apr 16 14:39:18 BST 2013 restarting VDR
Apr 16 14:39:19 alarmpi runvdr[219]: vdr: no fonts available - OSD will not show any text!
')
this is the error i always get
has this something to do with my dvb driver? i tried driver from homepage and aur, but tvheadend works without problems.

[hydro]

You could investigate the core dump.
https://wiki.archlinux.org/index.php/St ... ging_Guide

[fishxz]

i cant find a core file. even with "ulimit -c unlimited" i dont get a core file.

$this->bbcode_second_pass_code('', 'LD_DEBUG=files vdr > vdr.log 2>&1')
http://pastebin.com/wgm2Jqh6

[hydro]

The vdr.log looks quiet similar to the one I get, including the gconv symbol lookup errors, so this should not be the problem. But the gdb backtrace you posted before editing helped me reproducing the segfault on the DockStar:

- I use my 1.7.33 package. The /etc/conf.d/vdr holds some options that must be passed to gdb.
- I removed my existing /etc/vdr/setup.conf, it's not part of the vdr package.
- I removed any fonts installed
$this->bbcode_second_pass_code('', '
[root@alarm etc]# gdb --args vdr --config=/etc/vdr --lib=/usr/lib/vdr --localedir=/usr/share/locale
[...]
(gdb) r
Starting program: /usr/bin/vdr --config=/etc/vdr --lib=/usr/lib/vdr --localedir=/usr/share/locale
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
vdr: no fonts available - OSD will not show any text!
[New Thread 0x40f70460 (LWP 13028)]
[New Thread 0x41770460 (LWP 13029)]
[New Thread 0x420ff460 (LWP 13030)]
[Thread 0x40f70460 (LWP 13028) exited]
[Thread 0x41770460 (LWP 13029) exited]
[New Thread 0x41770460 (LWP 13032)]
[New Thread 0x40f70460 (LWP 13033)]
[New Thread 0x429ff460 (LWP 13034)]

Program received signal SIGSEGV, Segmentation fault.
0x000c7cb4 in ?? ()
(gdb) bt full
#0 0x000c7cb4 in ?? ()
No symbol table info available.
#1 0x000c848c in cSkinLCARSDisplayChannel::cSkinLCARSDisplayChannel(bool) ()
No symbol table info available.
#2 0x000c8b9c in cSkinLCARS::DisplayChannel(bool) ()
No symbol table info available.
#3 0x0009c138 in cDisplayChannel::cDisplayChannel(int, bool) ()
No symbol table info available.
#4 0x0005f4b8 in main ()
No symbol table info available.
')
This does not happen if either a font is installed or /etc/vdr/setup.conf does already exist.

Edit: crossposting...

[fishxz]

yes, thank u. thats the solution. what is the different from ur source to the aur source?

[hydro]

I never used the aur packages, so I really can't say. azleifel maintains packages for the stable vdr version. The latest stable version 2.0.0 was released only two weeks ago. The previous stable version 1.6.0 dated back to 2008. That's why I preferred to use the developer version 1.7.x for over two years. My packages were meant to be some sort of alternative draft to the archvdr project that tries to port e-tobi's Debian packages for a full-blown VDR to Arch Linux: I excluded dependencies that don't make sense on headless devices and focused only on a few plugins.
Back to your question: From azleifel's vdr.install file one obvious difference to my package is: I keep /video and /etc/vdr/ as default recording and config directory instead of the new default /srv/vdr/video and /var/lib/vdr. Another difference is I have split the runvdr.template to a ready-to-use /usr/bin/runvdr script and it's configuration file /etc/conf.d/vdr, while the aur package expects you to provide and edit a runvdr script.