Suggested advisory: ============ Updated VDR and VDR Live plugin packages fix path and permission issues related to VDR cache and plugin resource directories that prevented VDR from starting up on some configurations on fresh installations and VDR Live plugin from starting up in general. ============ Updated packages are in mga4 core/updates_testing. Testing notes: ============ 1. Install VDR. Minimum/easiest dummy installation is probably installing packages "vdr vdr-plugin-xineliboutput xineliboutput-local-sxfe" with no additional configuration. If that does not work, try setting REMOTE_PORT=2131 (or something) in /etc/sysconfig/vdr-xineliboutput. 2. Install VDR Live plugin: vdr-plugin-live. 3. Try to start up vdr (service vdr start) and monitor the system log (e.g. "journalctl -f"). Results with old packages: - VDR dies with either of these error messages: (a) tammi 05 01:27:53 sigma.onse.fi vdr[14674]: [14674] ERROR (tools.c,1604): /var/cache/vdr/epg.data.$$$: Permission denied tammi 05 01:27:53 sigma.onse.fi vdr[14674]: [14674] ERROR (epg.c,1268): Permission denied tammi 05 01:27:53 sigma.onse.fi vdr[14674]: [14674] exiting, exit code 2 (b) tammi 05 01:34:31 sigma.onse.fi vdr[15388]: [15388] ERROR (tools.c,411): /usr/share/vdr/plugins/live: Permission denied Results with fixed packages: - VDR process does not die, but continues running in the background. ============ Source packages: vdr-2.0.3-3.1.mga4 vdr-plugin-live-0.3.0-2.1.mga4 Binary packages: vdr-2.0.3-3.1.mga4 vdr-common-2.0.3-3.1.mga4 vdr-devel-2.0.3-3.1.mga4 vdr-plugin-dvbhddevice-2.0.3-3.1.mga4 vdr-plugin-dvbsddevice-2.0.3-3.1.mga4 vdr-plugin-epgtableid0-2.0.3-3.1.mga4 vdr-plugin-hello-2.0.3-3.1.mga4 vdr-plugin-osddemo-2.0.3-3.1.mga4 vdr-plugin-rcu-2.0.3-3.1.mga4 vdr-plugin-skincurses-2.0.3-3.1.mga4 vdr-plugin-status-2.0.3-3.1.mga4 vdr-plugin-servicedemo-2.0.3-3.1.mga4 vdr-plugin-svdrpdemo-2.0.3-3.1.mga4 vdr-plugin-pictures-2.0.3-3.1.mga4 vdr-plugin-live-0.3.0-2.1.mga4
Created attachment 5800 [details] output of journalctl -f
CC: (none) => herman.viaene
MGA4-64 on HP Probook 6555b KDE with Genius TV-Go usb, recognized with module âdvb_usb_rtl28xxu. No installation issues, but vdr services keeps dying, see attached file. Note: I also tried running vdr itself, after having assured that the user is member of the group vdr (and rebooting the PC): vdr vdr: can't access video directory /var/lib/vdr/video Surely the user sees all files and directories in /var/lib/vdr/ but cannot write as group privileges are read only.
Any advice for Herman to aid in testing Anssi please?
Installed packages from Core release on 64bit machine with PCTV 290e (USB). vdr started as a service and journalctl -f produced a listing similar to attachment 5800 [details]. So that reproduces the bug. Shall try later after updates testing installation.
CC: (none) => tarazed25
Created attachment 5836 [details] journalctl output for vdr server
Updated the installed packages from testing repository and started the vdr server OK. (There was a hitch because vlc was using the DVB-T2 device - killed that and things started happening) The attached log output shows a problem with on screen display. /var/lib/vdr now populated. User command vdr fails, as Herman found. Back to the fine manual.
'usermod -a -G vdr lcl' does not help. Still no access to video directory. [lcl@belexeuli ~]$ ls -l /var/lib/vdr total 12 drwxr-xr-x 3 vdr vdr 4096 Jan 25 17:25 config drwxr-xr-x 2 vdr vdr 4096 Jan 25 17:25 themes drwxr-xr-x 2 vdr vdr 4096 Jan 4 23:14 video /var/lib is owned by root.
Installed the xine components referred to in Testing Notes above. This involved the media sources Core Release and Tainted Release. Monitored journal entries and launched the server under root. Ran vdr as user and hit the "no access to video" error. Ran vdr as root. The journal output showed that things were happening but also recorded that "no OSD provider available...." See attachment for journalctl log.
Created attachment 5837 [details] more vdr log info
Tried setting the VDR_VIDEO parameter in /etc/sysconfig/vdr to a directory in user space then restarted the server and ran vdr -P xineliboutput as a user. The same error came up: vdr: can't access video directory /var/lib/vdr/video However, under root, the OSD interface appears so it is probably a fair assumption that it would work for a user providing she had access to the /var/lib/vdr/video directory.
Also tried explicitly adding user to video group. No progress. [root@belexeuli vdr]# grep vdr /etc/group video:x:82:vdr vdr:x:415:lcl [root@belexeuli vdr]# usermod -a -G video lcl [root@belexeuli vdr]# id lcl uid=500(lcl) gid=500(lcl) groups=500(lcl),82(video),415(vdr) [root@belexeuli vdr]# service vdr status vdr.service - LSB: Video Disk Recorder Loaded: loaded (/etc/rc.d/init.d/vdr) Active: active (running) since Mon 2015-01-26 02:05:09 GMT; 19min ago Process: 3714 ExecStop=/etc/rc.d/init.d/vdr stop (code=exited, status=0/SUCCESS) Process: 4530 ExecStart=/etc/rc.d/init.d/vdr start (code=exited, status=0/SUCCESS) CGroup: /system.slice/vdr.service ââ 1219 gpg-agent --keep-display --daemon --write-env-file /.gnupg/gpg-agent-in... ââ 3582 gpg-agent --keep-display --daemon --write-env-file /.gnupg/gpg-agent-in... ââ 4570 gpg-agent --keep-display --daemon --write-env-file /.gnupg/gpg-agent-in... ââ25250 gpg-agent --keep-display --daemon --write-env-file /.gnupg/gpg-agent-in... ââ32310 gpg-agent --keep-display --daemon --write-env-file /.gnupg/gpg-agent-in... Jan 26 02:05:09 belexeuli vdr[4530]: Starting Video Disk Recorder: gpg-agent[4569]: err...ory Jan 26 02:05:09 belexeuli vdr[4530]: [ OK ] Jan 26 02:05:09 belexeuli systemd[1]: Started LSB: Video Disk Recorder. Jan 26 02:05:09 belexeuli runvdr[4574]: Started runvdr for vdr Jan 26 02:05:09 belexeuli runvdr[4574]: Starting Video Disk Recorder [ status hello svd...s ] Jan 26 02:05:09 belexeuli vdr[4636]: [4636] ERROR: can't access /home/lcl/data/video
Reverted to default path for video directory and changed the access permissions to 777. That allowed a user to start vdr and also display the OSD window. That is probably enough to allow validation.
Whiteboard: (none) => has_procedure
Question:the update of vdr does not seem to break anything else, but the package as is does not work. IMHO, setting the access permissions to 777, when the /var/lib/vdr is owned by user and group vdr (and the current user is in the vdr group) should not be done. But I guess it is not our role to debug the package itself?????? In that case, you go along to validate.
I agree. My conclusion was premature. A user should really have her own configuration file so as to have access to a local directory for storage. Need to ask my mentor for an opinion.
Sorry about the delay, I'll look over your comments this evening and probably provide fixed packages for testing. Thanks for testing it.
(In reply to Herman Viaene from comment #1) > Created attachment 5800 [details] > output of journalctl -f > MGA4-64 on HP Probook 6555b KDE with Genius TV-Go usb, recognized with > module âdvb_usb_rtl28xxu. > No installation issues, but vdr services keeps dying, see attached file. Log shows you have installed all the built plugins. Unfortunately some of the plugins are not plug-and-play (requiring additional configuration) and therefore cause the startup to fail ("Error opening terminal: unknown" in your case caused by vdr-plugin-skincurses which is a terminal-only skin). Uninstall vdr-plugin-skincurses and the issue should disappear. (In reply to Herman Viaene from comment #2) > Note: I also tried running vdr itself, after having assured that the user is > member of the group vdr (and rebooting the PC): > vdr > vdr: can't access video directory /var/lib/vdr/video > Surely the user sees all files and directories in /var/lib/vdr/ but cannot > write as group privileges are read only. Yes, running VDR directly a normal user (instead of using the provided service) without extra configuration is not expected to work. (In reply to Len Lawrence from comment #10) > Tried setting the VDR_VIDEO parameter in /etc/sysconfig/vdr to a directory > in user space then restarted the server and ran vdr -P xineliboutput as a > user. The same error came up: > > vdr: can't access video directory /var/lib/vdr/video > > However, under root, the OSD interface appears so it is probably a fair > assumption that it would work for a user providing she had access to the > /var/lib/vdr/video directory. /etc/sysconfig/vdr configures the VDR systemd service, and has no effect if you run vdr directly. As noted above, running it directly requires much more manual configuration, and is not really the intended use. As for the vdr service, I believe you have the same issue with the service as Herman (having vdr-plugin-skincurses installed without configuring it blocks VDR from starting up).
Created attachment 5838 [details] vdr test log 3
Thanks Anssi, removed skincurses plugin and ran vdr service start The journalctl file (5838) reports a configuration error now. Maybe something has been corrupted by my earlier experiments. I might have to reinstall for a pristine configuration.
Did you try setting e.g. REMOTE_PORT=2131 in /etc/sysconfig/vdr-xineliboutput as noted in the description? I believe it should fix the issue in the latest log. (Looks like the local frontend startup is failing due to X server permission issues - my bad, I shouldn't have suggested that since it isn't plug-and-play either :) )
Yes, I tried that a couple of minutes ago and also removed the rcu plugin because there is no remote control. Jan 26 22:16:55 belexeuli vdr[1168]: [1178] [xine..put] Have CAP_SYS_NICE capability Jan 26 22:16:55 belexeuli vdr[1168]: [1178] [xine..put] cXinelibServer priority set suc...99] Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] xineliboutput: plugin file is /...0.1 Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] Searching frontend sxfe from /u...dr/ Jan 26 22:16:55 belexeuli vdr[1168]: [1178] [xine..put] Listening on port 2131 Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] Probing /usr/lib64/vdr/libxinel...1.0 Jan 26 22:16:55 belexeuli vdr[1168]: [1178] [xine..put] Listening for UDP broadcasts on...131 Jan 26 22:16:55 belexeuli vdr[1168]: [1176] [live] INFO: attempt to listen on ip = '' Jan 26 22:16:55 belexeuli vdr[1168]: [117B blob data] Jan 26 22:16:55 belexeuli vdr[1168]: [1176] [live] ERROR: Unable to load cert/key (/etc...ess Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] load_frontend: entry at 0x7f3a4...c20 Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] Using frontend sxfe (X11 (sxfe)...1.0 Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] cXinelibLocal::Action - fe created Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] sxfe_display_open(width=720, he....0) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] sxfe_display_open: failed to co....0) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] (ERROR (xine_sxfe_frontend.c...ry) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] sxfe_display_open: failed to co....0) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] (ERROR (xine_sxfe_frontend.c...le) Jan 26 22:16:55 belexeuli runvdr[1108]: No protocol specified Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] sxfe_display_open: failed to co...0.0 Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] (ERROR (xine_sxfe_frontend.c...ed) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] sxfe_display_open: failed to co...er. Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] (ERROR (xine_sxfe_frontend.c...ed) Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [vdr-sxfe] If X server is running, try run...dow Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] cXinelibLocal: Error initializi...lay Jan 26 22:16:55 belexeuli vdr[1168]: [1177] [xine..put] cXinelibLocal::Action: thread f...hed Jan 26 22:16:55 belexeuli vdr[1168]: [1177] Local decoder/display (cXinelibThread) thre...77) Jan 26 22:16:56 belexeuli vdr[1168]: [1168] [xine..put] cXinelibDevice::Start(): Local ...led Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: osddemo Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: live Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: svccli Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: epgtableid0 Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: dvbhddevice Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: svcsvr Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: dvbsddevice Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: svdrpdemo Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: hello Jan 26 22:16:56 belexeuli vdr[1168]: [1168] stopping plugin: status Jan 26 22:16:56 belexeuli vdr[1168]: [1168] [xine..put] cXinelibOsdProvider: shutting down ! Jan 26 22:16:56 belexeuli vdr[1168]: [1174] section handler thread ended (pid=1168, tid=1174) Jan 26 22:16:56 belexeuli vdr[1168]: [1173] tuner on frontend 0/0 thread ended (pid=116...73) Jan 26 22:16:56 belexeuli vdr[1168]: [1168] [xine..put] cXinelibDevice::StopDevice(): S...... Jan 26 22:16:57 belexeuli vdr[1168]: [1178] Remote decoder/display server (cXinelibServ...78) Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: pictures Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: xineliboutput Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: osddemo Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: live Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: svccli Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: epgtableid0 Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: dvbhddevice Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: svcsvr Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: dvbsddevice Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: svdrpdemo Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: hello Jan 26 22:16:57 belexeuli vdr[1168]: [1168] deleting plugin: status Jan 26 22:16:57 belexeuli vdr[1168]: [1168] exiting, exit code 2 Jan 26 22:16:57 belexeuli runvdr[1108]: VDR configuration error
Created attachment 5839 [details] vdr test with xhost+
Attachment 5838 is obsolete: 0 => 1
Back in business. OSD panel appears and event loop starts.
Ensured that the system worked when the permissions on /var/lib/vdr/video reverted to the original 755.
In VirtualBox, M4, KDE, 32-bit Package(s) under test: vdr vdr-plugin-live default install of vdr & vdr-plugin-live [root@localhost wilcal]# urpmi vdr Package vdr-2.0.3-3.mga4.i586 is already installed [root@localhost wilcal]# urpmi vdr-plugin-live Package vdr-plugin-live-0.3.0-2.mga4.i586 is already installed From: http://en.wikipedia.org/wiki/Video_Disk_Recorder "The computer needs to be equipped with a digital TV tuner card." Is this an absolute to test this application or can it record a vimeo video being streamed? How do you launch it? It does not seem to create a launcher in the Menu. I started vdr from MCC -> System -> Manage system services then played a https://vimeo.com/ video and nothing got recorded in: /var/lib/vdr/video. I'm missing something here? Thanks Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
CC: (none) => wilcal.int
Herman and I have been testing the update recently. On the backburner just now. I got as far as the OSD window but did not have an appropriate plugin for vlc or kaffeine which are the two applications I use for watching TV on screen. Had not thought of streaming - assumed that vdr required a tv tuner to work. It would launch even though vlc or whatever had already grabbed the tuner, AFAICR. My impression was that it at least needed the tuner to obtain the EPG. journalctl -f to see what is going on. su - service vdr start to start vdr with the on screen display.
(In reply to Len Lawrence from comment #25) > My impression was that it at least needed the tuner to > obtain the.... Rats, I got interested because of the maybe opportunity to capture streaming videos like from YouTube.
I guess it would need another plugin but also maybe something to emulate a capture card, built-in?
Whiteboard: has_procedure => has_procedure mga4-64-ok
Back to comment 16 : I removed the skincurses plugin , started vdr service and now I get from journalctl: [22276] VDR version 2.0.3 (2.0.3-3.1.mga4) started [22276] codeset is 'UTF-8' - known [22276] found 0 locales in /usr/share/locale [22276] no locale for language code 'deu,ger' ....and some more of these... [22276] loading /var/lib/vdr/config/setup.conf [22276] loading /var/lib/vdr/config/sources.conf [22276] loading /var/lib/vdr/config/diseqc.conf [22276] loading /var/lib/vdr/config/scr.conf [22276] loading /var/lib/vdr/config/channels.conf [22276] loading /var/lib/vdr/config/svdrphosts.conf [22276] loading /var/lib/vdr/config/keymacros.conf [22276] registered source parameters for 'A - ATSC' [22276] registered source parameters for 'C - DVB-C' [22278] video directory scanner thread started (pid=22276, tid=22278, prio=high) [22279] video directory scanner thread started (pid=22276, tid=22279, prio=high) [22276] registered source parameters for 'S - DVB-S' [22276] registered source parameters for 'T - DVB-T' [22278] video directory scanner thread ended (pid=22276, tid=22278) [22279] video directory scanner thread ended (pid=22276, tid=22279) [22276] probing /dev/dvb/adapter0/frontend0 [22276] creating cDvbDevice [22276] new device number 1 [22276] ERROR: can't open DVB device 0/0 [22276] found 1 DVB device [22281] section handler thread started (pid=22276, tid=22281, prio=low) [22280] epg data reader thread started (pid=22276, tid=22280, prio=high) [22276] setting primary device to 1 [22280] reading EPG data from /var/cache/vdr/epg.data [22276] device 1 has no MPEG decoder [22276] assuming manual start of VDR [22280] epg data reader thread ended (pid=22276, tid=22280) [22276] SVDRP listening on port 6419 [22276] setting current skin to "lcars" [22276] loading /var/lib/vdr/config/themes/lcars-default.theme [22276] remote control KBD - learning keys [22282] KBD remote control thread started (pid=22276, tid=22282, prio=high) [22282] cTimeMs: using monotonic clock (resolution is 1 ns) [22276] ERROR: no OSD provider available - using dummy OSD! So no more error that vdr dies. OK for me.
Testing MGA4-32 on AcerD620 Omitted installation of skincurses plugin. Used same Genius TV-Go usb, recognized with module âdvb_usb_rtl28xxu. output of journalctl after service vdr start : Starting LSB: Video Disk Recorder... 4131]: Starting Video Disk Recorder: gpg-agent[4160]: error creating `/.gnupg/gpg-ag...ectory [4131]: [ OK ] [1]: Started LSB: Video Disk Recorder. [4163]: Started runvdr for vdr [4163]: Starting Video Disk Recorder [ status svdrpdemo hello dvbsddevice svcsvr r...ures ] [4218]: [4218] VDR version 2.0.3 (2.0.3-3.1.mga4) started [4218] switched to user 'vdr' [4218] codeset is 'UTF-8' - known [4218] found 0 locales in /usr/share/locale [4218] no locale for language code 'deu,ger' ... and more of those.... [4218] loading plugin: /usr/lib/vdr/libvdr-status.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-svdrpdemo.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-hello.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-dvbsddevice.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-svcsvr.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-rcu.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-dvbhddevice.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-epgtableid0.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-svccli.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-live.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-osddemo.so.2.0.0.1 [4218] loading plugin: /usr/lib/vdr/libvdr-pictures.so.2.0.0.1 [4218] loading /var/lib/vdr/config/setup.conf [4218] loading /var/lib/vdr/config/sources.conf [4218] loading /var/lib/vdr/config/diseqc.conf [4218] loading /var/lib/vdr/config/scr.conf [4218] loading /var/lib/vdr/config/channels.conf [4218] loading /var/lib/vdr/config/svdrphosts.conf [4218] loading /var/lib/vdr/config/keymacros.conf [4218] registered source parameters for 'A - ATSC' [4218] registered source parameters for 'C - DVB-C' [4218] registered source parameters for 'S - DVB-S' [4218] registered source parameters for 'T - DVB-T' [4218] probing /dev/dvb/adapter0/frontend0 [4218] creating cDvbDevice [4218] new device number 1 [4221] epg data reader thread started (pid=4218, tid=4221, prio=high) [4221] reading EPG data from /var/cache/vdr/epg.data [4221] epg data reader thread ended (pid=4218, tid=4221) [4220] video directory scanner thread started (pid=4218, tid=4220, prio=high) [4220] video directory scanner thread ended (pid=4218, tid=4220) [4219] video directory scanner thread started (pid=4218, tid=4219, prio=high) [4219] video directory scanner thread ended (pid=4218, tid=4219) [4218] DVB API version is 0x050A (VDR was built with 0x050A) [4218] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 ("Realtek RTL2832 (DVB-T)") [4218] found 1 DVB device [4218] initializing plugin: status (2.0.0): Status monitor test [4218] initializing plugin: svdrpdemo (2.0.0): How to add SVDRP support to a plugin [4218] initializing plugin: hello (2.0.0): A friendly greeting [4218] initializing plugin: dvbsddevice (2.0.1): SD Full Featured DVB device [4218] initializing plugin: svcsvr (2.0.0): Service demo server 4218] initializing plugin: rcu (2.0.0): Remote Control Unit [4218] initializing plugin: dvbhddevice (2.0.2): HD Full Featured DVB device [4218] initializing plugin: epgtableid0 (2.0.0): EPG handler for events with ...d 0x00 [4218] initializing plugin: svccli (2.0.0): Service demo client [4218] initializing plugin: live (0.3.0): Live Interactive VDR Environment [4218] initializing plugin: osddemo (2.0.0): Demo of arbitrary OSD setup [4218] initializing plugin: pictures (2.0.0): A simple picture viewer [4218] setting primary device to 1 [4218] device 1 has no MPEG decoder [4218] assuming manual start of VDR [4218] SVDRP listening on port 6419 [4218] setting current skin to "lcars" [4218] loading /var/lib/vdr/config/themes/lcars-default.theme [4218] starting plugin: status [4218] starting plugin: svdrpdemo [4218] starting plugin: hello [4218] starting plugin: dvbsddevice [4218] starting plugin: svcsvr [4218] starting plugin: rcu [4218] ERROR (rcu.c,87): /dev/ttyS1: Permission denied [4218] starting plugin: dvbhddevice [4218] starting plugin: epgtableid0 [4218] starting plugin: svccli [4218] starting plugin: live [4224] section handler thread started (pid=4218, tid=4224, prio=low) [4223] tuner on frontend 0/0 thread started (pid=4218, tid=4223, prio=high) [4223] cTimeMs: using monotonic clock (resolution is 1 ns) [4218] LIVE: initial file cache has 82 entries and needs 377394 bytes of data! [4218] starting plugin: osddemo [4218] starting plugin: pictures [4218] ERROR: remote control RCU not ready! [4218] status: cStatusTest::SetVolume 255 1 [4225] [live] INFO: attempt to listen on ip = '' 4225] [live] ERROR: Unable to load cert/key (/etc/pki/tls/private/vdr-live.p...uccess [4218] OSD size changed to 720x480 @ 1 [4218] ERROR: no OSD provider available - using dummy OSD! [4218] status: cStatusTest::OsdClear and vdr keeeps running.
Whiteboard: has_procedure mga4-64-ok => has_procedure MGA4-64-OK MGA-32-OK
Thanks guys. Advisory uploaded. Validating. Could sysadmin please push to4 updates Thanks
Keywords: (none) => validated_updateWhiteboard: has_procedure MGA4-64-OK MGA-32-OK => has_procedure advisory MGA4-64-OK MGA-32-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0009.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED