Segfault unter Fedora20

MerlinElMago · 6. Januar 2014

Hallöchen liebe Freunde,
ich habe nach langer Zeit mal wieder ein Bisschen zu basteln angefanden. Ich habe einen Celeron Rechner mit zwei Budget Karten bestückt (DVB-S & DVB-T) um diesen nun als Streamserver für XBMC zu benutzen (da ja jeder jetzt darüber redet wie schön das alles funktioniert). Ich habe das neueste stable Release genommen und auf einer Fedora 20 installiert. Ich habe nur ein einziges Plugin und zwar dummydevice und bekomme einen segfault wenn ich den VDR starte. Ich hatte zuerst die Firmware in Verdacht, aber irgendwie kann das Problem dort ja wohl auch nicht liegen.

Mein Log:

Code

ene 06 17:51:49 localhost.localdomain vdr[998]: [998] VDR version 2.0.4 started
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] codeset is 'UTF-8' - known
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] found 28 locales in /usr/local/share/locale
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading plugin: /usr/local/lib/vdr/libvdr-dummydevice.so.2.0.0
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/sources.conf
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/diseqc.conf
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/scr.conf
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/channels.conf
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/svdrphosts.conf
ene 06 17:51:49 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/keymacros.conf
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] ERROR: no fonts available - OSD will not show any text!
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] registered source parameters for 'A - ATSC'
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] registered source parameters for 'C - DVB-C'
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] registered source parameters for 'S - DVB-S'
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] registered source parameters for 'T - DVB-T'
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] probing /dev/dvb/adapter0/frontend0
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] creating cDvbDevice
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] new device number 1
ene 06 17:51:50 localhost.localdomain vdr[998]: [1001] epg data reader thread started (pid=998, tid=1001, prio=high)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1000] video directory scanner thread started (pid=998, tid=1000, prio=high)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1000] video directory scanner thread ended (pid=998, tid=1000)
ene 06 17:51:50 localhost.localdomain vdr[998]: [999] video directory scanner thread started (pid=998, tid=999, prio=high)
ene 06 17:51:50 localhost.localdomain vdr[998]: [999] video directory scanner thread ended (pid=998, tid=999)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1001] epg data reader thread ended (pid=998, tid=1001)
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] DVB API version is 0x050A (VDR was built with 0x050A)
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] frontend 0/0 provides DVB-S with QPSK ("ST STV0299 DVB-S")
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] probing /dev/dvb/adapter1/frontend0
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] creating cDvbDevice
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] new device number 2
ene 06 17:51:50 localhost.localdomain vdr[998]: [1004] section handler thread started (pid=998, tid=1004, prio=low)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1003] tuner on frontend 0/0 thread started (pid=998, tid=1003, prio=high)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1003] cTimeMs: using monotonic clock (resolution is 1 ns)
ene 06 17:51:50 localhost.localdomain kernel: tda1004x: setting up plls for 53MHz sampling clock
ene 06 17:51:50 localhost.localdomain kernel: tda1004x: found firmware revision 29 -- ok
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] frontend 1/0 provides DVB-T with QPSK,QAM16,QAM64 ("Philips TDA10046H DVB-T")
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] found 2 DVB devices
ene 06 17:51:50 localhost.localdomain vdr[998]: [1007] section handler thread started (pid=998, tid=1007, prio=low)
ene 06 17:51:50 localhost.localdomain vdr[998]: [1006] tuner on frontend 1/0 thread started (pid=998, tid=1006, prio=high)
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] initializing plugin: dummydevice (2.0.0): Output device that does nothing
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] new device number 9
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] setting primary device to 1
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] device 1 has no MPEG decoder
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] trying device number 3 instead
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] setting primary device to 3
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] assuming manual start of VDR
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] SVDRP listening on port 6419
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] setting current skin to "lcars"
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] loading /var/lib/vdr/themes/lcars-default.theme
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] starting plugin: dummydevice
ene 06 17:51:50 localhost.localdomain vdr[998]: [998] remote control KBD - learning keys
ene 06 17:51:50 localhost.localdomain vdr[998]: [1008] KBD remote control thread started (pid=998, tid=1008, prio=high)
ene 06 17:51:50 localhost.localdomain kernel: vdr[998]: segfault at 0 ip 0812ba88 sp bfbcc530 error 4 in vdr[8048000+166000]

Alles anzeigen

Hat vielleicht jemand 'ne Idee?

Gruss
Merlin

mini73 · 6. Januar 2014

Am besten mal mit Debugsymbolen übersetzen (falls du sie stripst), "ulimit -c unlimited" vorher ausführen und dann mit "--userdump" auf der Konsole starten, damit ein coredump geschrieben wird.
Und dann mit gdb einen Backtrace erzeugen, damit man sieht, wo genau er da abstürzt.

Lars.

mini73 · 6. Januar 2014

Hast du eine remote.conf? Wenn nicht, dann versucht der vdr deine Fernbedienung anzulernen (das ist zumindest die nächste Zeile in vdr.c nach "new cKbdRemote;".
Wenn du den vdr über systemd als service starten lässt, füge sonst mal "--no-kbd" hinzu.

Trotzdem sollte man den Absturz untersuchen, damit sowas abgefangen werden kann.

Lars.

MerlinElMago · 6. Januar 2014

Also die --no-kbd Option ändert schonmal nichts am Segfault.

Könntest Du mir bitte genau beschreiben wie ich einen Dump erzeuge? Hab' ich nämlich noch nie gemacht

Code

ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] VDR version 2.0.4 started
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] codeset is 'UTF-8' - known
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] found 28 locales in /usr/local/share/locale
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading plugin: /usr/local/lib/vdr/libvdr-dummydevice.so.2.0.0
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/sources.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/diseqc.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/scr.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/channels.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/svdrphosts.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/keymacros.conf
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] ERROR: no fonts available - OSD will not show any text!
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] registered source parameters for 'A - ATSC'
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] registered source parameters for 'C - DVB-C'
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] registered source parameters for 'S - DVB-S'
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] registered source parameters for 'T - DVB-T'
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] probing /dev/dvb/adapter0/frontend0
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] creating cDvbDevice
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] new device number 1
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1306] epg data reader thread started (pid=1303, tid=1306, prio=high)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1306] epg data reader thread ended (pid=1303, tid=1306)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1305] video directory scanner thread started (pid=1303, tid=1305, prio=high)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1305] video directory scanner thread ended (pid=1303, tid=1305)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1304] video directory scanner thread started (pid=1303, tid=1304, prio=high)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1304] video directory scanner thread ended (pid=1303, tid=1304)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] DVB API version is 0x050A (VDR was built with 0x050A)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] frontend 0/0 provides DVB-S with QPSK ("ST STV0299 DVB-S")
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] probing /dev/dvb/adapter1/frontend0
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] creating cDvbDevice
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1303] new device number 2
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1309] section handler thread started (pid=1303, tid=1309, prio=low)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1308] tuner on frontend 0/0 thread started (pid=1303, tid=1308, prio=high)
ene 06 18:29:41 localhost.localdomain vdr[1303]: [1308] cTimeMs: using monotonic clock (resolution is 1 ns)
ene 06 18:29:41 localhost.localdomain kernel: tda1004x: setting up plls for 53MHz sampling clock
ene 06 18:29:42 localhost.localdomain kernel: tda1004x: found firmware revision 29 -- ok
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] frontend 1/0 provides DVB-T with QPSK,QAM16,QAM64 ("Philips TDA10046H DVB-T")
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] found 2 DVB devices
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] initializing plugin: dummydevice (2.0.0): Output device that does nothing
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] new device number 9
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] setting primary device to 1
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] device 1 has no MPEG decoder
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] trying device number 3 instead
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] setting primary device to 3
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] assuming manual start of VDR
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] SVDRP listening on port 6419
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] setting current skin to "lcars"
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] loading /var/lib/vdr/themes/lcars-default.theme
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] starting plugin: dummydevice
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] switching to channel 1
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1312] section handler thread started (pid=1303, tid=1312, prio=low)
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1311] tuner on frontend 1/0 thread started (pid=1303, tid=1311, prio=high)
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1313] receiver on device 1 thread started (pid=1303, tid=1313, prio=high)
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1314] TS buffer on device 1 thread started (pid=1303, tid=1314, prio=high)
ene 06 18:29:42 localhost.localdomain vdr[1303]: [1303] OSD size changed to 720x480 @ 1
ene 06 18:29:42 localhost.localdomain kernel: vdr[1303]: segfault at 0 ip 08129708 sp bfa2d270 error 4 in vdr[8048000+166000]

Alles anzeigen

Gruss
Merlin

mini73 · 6. Januar 2014

Er scheint aber schon ein wenig weiter zu kommen.
Ich bin mir nicht sicher, ob dummydevice noch nötig ist, probier's mal ohne.

Sammelt systemd nicht vielleicht schon automatisch einen coredump ein? Frag mal journalctl.
Ansonsten den vdr einfach mal mit "--userdump" starten, vielleicht kommt dann einer.
Wo man bei Fedora das "ulimit -c unlimited" festlegt, weiß ich nicht genau. Im Zweifel sonst den vdr einfach in einer Shell manuell starten (als root):

Code

ulimit -c unlimited
vdr --userdump <und sonstige Optionen>

Lars.

MerlinElMago · 6. Januar 2014

Jetzt habe ich vdr mit --userdump als root gestartet.

Code

ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] VDR version 2.0.4 started
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] codeset is 'UTF-8' - known
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] found 28 locales in /usr/local/share/locale
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/sources.conf
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/diseqc.conf
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/scr.conf
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/channels.conf
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/svdrphosts.conf
ene 06 18:54:24 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/keymacros.conf
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] ERROR: no fonts available - OSD will not show any text!
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] registered source parameters for 'A - ATSC'
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] registered source parameters for 'C - DVB-C'
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] registered source parameters for 'S - DVB-S'
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] registered source parameters for 'T - DVB-T'
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] probing /dev/dvb/adapter0/frontend0
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] creating cDvbDevice
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] new device number 1
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1366] epg data reader thread started (pid=1363, tid=1366, prio=high)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1366] epg data reader thread ended (pid=1363, tid=1366)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1365] video directory scanner thread started (pid=1363, tid=1365, prio=high)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1365] video directory scanner thread ended (pid=1363, tid=1365)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1364] video directory scanner thread started (pid=1363, tid=1364, prio=high)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1364] video directory scanner thread ended (pid=1363, tid=1364)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] DVB API version is 0x050A (VDR was built with 0x050A)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] frontend 0/0 provides DVB-S with QPSK ("ST STV0299 DVB-S")
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] probing /dev/dvb/adapter1/frontend0
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] creating cDvbDevice
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] new device number 2
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1369] section handler thread started (pid=1363, tid=1369, prio=low)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1368] tuner on frontend 0/0 thread started (pid=1363, tid=1368, prio=high)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1368] cTimeMs: using monotonic clock (resolution is 1 ns)
ene 06 18:54:25 localhost.localdomain kernel: tda1004x: setting up plls for 53MHz sampling clock
ene 06 18:54:25 localhost.localdomain kernel: tda1004x: found firmware revision 29 -- ok
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] frontend 1/0 provides DVB-T with QPSK,QAM16,QAM64 ("Philips TDA10046H DVB-T")
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] found 2 DVB devices
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] setting primary device to 1
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] device 1 has no MPEG decoder
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] assuming manual start of VDR
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] SVDRP listening on port 6419
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] setting current skin to "lcars"
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] loading /var/lib/vdr/themes/lcars-default.theme
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1363] remote control KBD - learning keys
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1372] section handler thread started (pid=1363, tid=1372, prio=low)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1373] KBD remote control thread started (pid=1363, tid=1373, prio=high)
ene 06 18:54:25 localhost.localdomain vdr[1363]: [1371] tuner on frontend 1/0 thread started (pid=1363, tid=1371, prio=high)
ene 06 18:54:25 localhost.localdomain kernel: vdr[1363]: segfault at 0 ip 0812ba88 sp bfabbd20 error 4 in vdr[8048000+166000]

Alles anzeigen

mini73 · 6. Januar 2014

Und liegt irgendwo ein coredump?
Wenn du ihn gefunden hast:

Code

gdb /usr/bin/vdr --core=/pfad/zu/coredump

Dann mit "bt full" einen Backtrace erzeugen.

Lars.

MerlinElMago · 6. Januar 2014

Habe einen 44MB grossen coredump.

Gruss
Merlin

mini73 · 6. Januar 2014

Cool.

Scheint unter systemd auch einfacher zu gehen:
http://www.freedesktop.org/sof…/systemd-coredumpctl.html
Also einfach mal versuchen:

Code

systemd-coredumpctl gdb /usr/bin/vdr

(wenn dein vdr unter /usr/bin liegt, ansonsten anpassen).

Lars.

MerlinElMago · 6. Januar 2014

Code

gdb /usr/local/bin/vdr --core=./core.1374
GNU gdb (GDB) Fedora 7.6.50.20130731-16.fc20
Copyright (C) 2013 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 "i686-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
..
Reading symbols from /usr/local/bin/vdr...done.
[New LWP 1374]
[New LWP 1379]
[New LWP 1380]
[New LWP 1384]
[New LWP 1382]
[New LWP 1383]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Core was generated by `vdr --userdump'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  CreateTinyFont (LineHeight=10) at skinlcars.c:228
228	      if (Height < 2 || TinyFont->Height() <= LineHeight)
Missing separate debuginfos, use: debuginfo-install expat-2.1.0-7.fc20.i686 fontconfig-2.11.0-1.fc20.i686 freetype-2.5.0-4.fc20.i686 glibc-2.18-11.fc20.i686 libattr-2.4.47-3.fc20.i686 libcap-2.22-7.fc20.i686 libgcc-4.8.2-7.fc20.i686 libjpeg-turbo-1.3.0-2.fc20.i686 libpng-1.6.3-3.fc20.i686 libstdc++-4.8.2-7.fc20.i686 zlib-1.2.8-3.fc20.i686

Alles anzeigen

mini73 · 6. Januar 2014

Dann sind die fehlenden Fonts ein Problem:

Code

ERROR: no fonts available - OSD will not show any text!

Deshalb bekommt der vdr wohl keine Fontgrößen und dann ist bestimmt "TinyFont" NULL.
Kannst du da mal

Code

print TinyFont

im gdb eingeben?

Lars.

MerlinElMago · 6. Januar 2014

Klar!
Resultat:

Code

$1 = (cFont *) 0x0

Gruss

mini73 · 6. Januar 2014

Dachte ich mir, ein Nullpointer.
Und wie sieht es ohne dummydevice aus?

Lars.

MerlinElMago · 6. Januar 2014

Das war die ganze Zeit ohne dummydevice! Soll ich's nochmal MIT dummydevice wiederholen?

mini73 · 6. Januar 2014

Ach so, 'tschuldigung.
Vermutlich wird's auch mit dummydevice abstürzen.

Du könntest ein anderes Skin in der setup.conf eintragen (z.B. classic). Vielleicht ist das weniger zimperlich.

Auf alle Fälle hast du einen Bug im vdr gefunden, dafür schon mal Glückwunsch.

Lars.

MerlinElMago · 6. Januar 2014

Naja, das ist ja eine zweifelhafte Ehre

Gugut, ich versuche es mal und melde!

mini73 · 6. Januar 2014

Oder du installierst einen Font. Wie ein passendes Paket dazu heißt, weiß ich allerdings nicht.

Lars.

mini73 · 6. Januar 2014

Du könntest kls davon berichten, ich muss jetzt leider weg.
lcars scheint nicht wirklich darauf ausgelegt zu sein, ohne Font zu arbeiten. Da wird's auch an anderen Stellen segfaults geben.

Lars.

MerlinElMago · 6. Januar 2014

Nebenbei bemerkt habe ich überhaupt keine setup.conf, weil ich ja das Ding noch nicht habe starten können...

mini73 · 6. Januar 2014

Einfach eine anlegen mit "OSDSkin = classic".

Lars

Segfault unter Fedora20

Jetzt mitmachen!

Teilen