Linux Player - 1.8 R2 Released

The team at Xibo Signage are pleased to announce that our second release of the new Xibo Player for Linux is ready. This release works with Xibo CMS version 1.8.12 or later.


This is a companion discussion topic for the original entry at https://blog.xibo.org.uk/linux-player-1-8-r2-released/

Hi Xibo devs! Glad to see another update on the linux platform, however it is still not working properly for me. I keep getting these errors (i’m running CMS 2.0.3):

xibo-player.options
[12:23:26.238] [004825] [debug]: Scheme: 1 HostType: 0 Host: cms.klinik-tv.dk Port: 443 Target: /xmds.php?v=5

(gst-plugin-scanner:5113): GStreamer-WARNING **: 12:23:29.111: Failed to load plugin '/snap/xibo-player/25/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstaasink.so': libgpm.so.2: cannot open shared object file: No such file or directory

(gst-plugin-scanner:5113): GStreamer-WARNING **: 12:23:29.581: Failed to load plugin '/snap/xibo-player/25/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstaasink.so': libgpm.so.2: cannot open shared object file: No such file or directory
[12:23:29.992] [005056] [error]: ScreenSaver wont'be suspended
[12:23:29.995] [005056] [debug]: http://127.0.0.1:1234/
[12:23:30.184] [005056] [debug]: Player settings updated
[12:23:30.185] [005120] [debug]: Collection started
[12:23:30.189] [005120] [debug]: Scheme: 1 HostType: 0 Host: cms.klinik-tv.dk Port: 443 Target: /xmds.php?v=5

(player:5056): glibmm-ERROR **: 12:23:37.851: 
unhandled exception (type std::exception) in signal handler:
what: /home/dentalmedia/snap/xibo-player/25/resources/60.xlf(10): unexpected end of data

Hi Devs,
displaying pdf files is working fine for me, but I have problems showing a web page with an embedded pdf file. There is only a white screen. I’m using CMS 2.0.4

Cheers,
Dustin

Thanks. We have an issue recorded to handle that better, but fundamentally the CMS shouldn’t be sending an incomplete XLF file, so it would be worth looking at what state the layout in question is in to understand why that is happening for you.

If it’s an external website, then all we’re doing is opening a browser and putting that webpage in it. It could be that the webpage uses some kind of plugin to render the PDF which doesn’t work well in Chromium?

It’s ultimately outside our control as it’s a third party webpage dictating how the page to be rendered.