Linux Player - 1.8 R4 Released

Xibo Signage are pleased to announce Xibo for Linux 1.8 R4, our fourth release of the new Linux Player.


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

Hi,

Following the update to 1.8 R4 I am getting the following error message every 4 seconds or so when trying to start xibo-player:

[1709] [debug]: [DBus] ScreenSaver is suspended: 1417081508 (different number each time)
[1709] [info]: [XiboApp] http://127.0.0.1.1234/
[1709] [debug]: [XiboApp] Player settings updated
teminate called after throwing an instance of ‘Gdk::PixbufError’
Player exited with code 6

Hello, i have the same problem with this new version 1.8 R4 … My all player are now on ubuntu 18.04 LTS in production and nothing work… i have try with autostart and systemd but nothing work :

  Active: active (running) since Fri 2019-11-22 18:00:55 CET; 22s ago
 Main PID: 575 (watchdog)
    Tasks: 1 (limit: 4525)
   CGroup: /system.slice/start-xibo.service
           └─575 /snap/xibo-player/37/bin/watchdog
    
nov. 22 18:01:17 fst-o-f-xibo2 xibo-player[575]: [18:01:17.070] [2158] [info]: [XiboApp] http://127.0.0.1:9696/
    nov. 22 18:01:17 fst-o-f-xibo2 xibo-player[575]: [18:01:17.117] [2158] [error]: [WindowGtk] Fullscreen mode hasn't been activated
    nov. 22 18:01:17 fst-o-f-xibo2 xibo-player[575]: [18:01:17.117] [2158] [error]: [XiboApp] Error while upadting settings: [WidgetGtk] Size should be non-negative
    nov. 22 18:01:17 fst-o-f-xibo2 player[2158]: Failed to set text '<markup><span size="18446744073709551599"></span></markup>' from markup due to error parsing markup: Value of 'size' attribute on <span> tag on line 1 could not be parsed;
    nov. 22 18:01:17 fst-o-f-xibo2 xibo-player[575]: [18:01:17.188] [2158] [error]: [Main] [WidgetGtk] Scale factor should be positive
    nov. 22 18:01:17 fst-o-f-xibo2 xibo-player[575]: Player exited with code 0

We can see the player is not loaded

But if i open a terminal, or open a folder, the process player is load :

 Active: active (running) since Fri 2019-11-22 18:00:55 CET; 4min 27s ago
 Main PID: 575 (watchdog)
    Tasks: 31 (limit: 4525)
   CGroup: /system.slice/start-xibo.service
           ├─ 575 /snap/xibo-player/37/bin/watchdog
           └─3390 /snap/xibo-player/37/bin/player
nov. 22 18:04:58 fst-o-f-xibo2 xibo-player[575]: [18:04:58.654] [3390] [info]: [XiboApp] http://127.0.0.1:9696/
nov. 22 18:04:58 fst-o-f-xibo2 player[3390]: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
nov. 22 18:05:01 fst-o-f-xibo2 player[3390]: console message: http://127.0.0.1:9696/pdf.js @9499: Warning: TT: undefined function: 32
nov. 22 18:05:09 fst-o-f-xibo2 player[3390]: console message: http://127.0.0.1:9696/pdf.js @9499: Warning: TT: undefined function: 32
nov. 22 18:05:20 fst-o-f-xibo2 player[3390]: console message: http://127.0.0.1:9696/pdf.js @9499: Warning: TT: undefined function: 32

With the 1.8 R3 everything work, could you roll back your version, or fix this version?
Have you got a plan for to blocked version on snap? Because when you send an update, snap verify every day if there is an update and apply it and if there is a bug we are blocked.

In your roadmap there is a binary for linux like windows?
Thanks.

+1 would be nice to be able to roll back to the previous version

Same issue with R4.
We’re running Intel Sticks with Debian 10 + X + nodm.
Interesting part - sticks that was previously deployed and updated from R3 - works fine. Trying to find a difference.

[14:11:26.538] [3346] [error]: [DBus] ScreenSaver wont'be suspended: org.freedesktop.DBus.Error.Spawn.ExecFailed
[14:11:26.539] [3346] [info]: [XiboApp] http://127.0.0.1:1234/
[14:11:26.645] [3346] [error]: [WindowGtk] Fullscreen mode hasn't been activated
(player:3346): Gtk-WARNING **: 14:11:26.645: Failed to set text '<markup><span size="18446744073709551599"></span></markup>' from markup due to error parsing markup: Value of 'size' attribute on <span> tag on line 1 could not be parsed; should be an integer no more than 2147483647, or a string such as 'small', not '18446744073709551599'
[14:11:26.646] [3346] [error]: [XiboApp] Error while upadting settings: [WidgetGtk] Size should be non-negative
[14:11:26.646] [3346] [error]: [Main] [ImageGtk] Size should be positive
Player exited with code 0

I resolved this by :

  • remove xibo-player by snap
  • erase the xibo-player dir in /home/user/snap
  • install xibo-player by snap

I scripted this to make it to every players.

Sincerly, this Snap solution is absolutely terrible as it is not possible to test an upgrade before deploying, and make so much injuries when we have a lot of client to manage.

For me solution was ‘manually place and fill playerSettings.xml in /home/user/snap/xibo-player/common/’.
For some reason resolution cannot be automatically determined by player or something like that.

I have the same PixBufError problem on our linux players. We are using Ubuntu 18

[08:53:12.007] [2853] [debug]: [DBus] ScreenSaver is suspended: 1557447748
[08:53:12.008] [2853] [info]: [XiboApp] http://127.0.0.1:1234/
[08:53:12.023] [2853] [debug]: [XiboApp] Player settings updated
terminate called after throwing an instance of ‘Gdk::PixbufError’
Player exited with code 6

I have tried setting the display setting profile width and height, reinstalling the player, placing playerSettings.xml manually but nothing i have tried has solved the issue for me.

solution is here by Walid_MOGHRABI :
“forcing the screen resolution in the profile setting for your display/display group.”
Setting the width and height worked for me.
it’s a short-term solution.

i’ve set the screen res on both display and display settings profile but it seemed to have no change…

Maybe i forgot 1 step.
When you add a display (existing or not) you need to start the player one time (manually). When it’s started you can changed the profile setting on this player ( in my case, i switch Linux to nothing, i save it and switch again, nothing to Linux. Wait 1-2 min and reboot. For me it’s work)

snap revert xibo-player

will roll you back to R3 if you had it installed previously.

There does appear to be an issue with the screen size not being correctly autodetected and we have a bug logged to look at that now. Fixing the screen resolution in the display settings profile should resolve it once you can get those settings pushed down to the Player - which may require you to open the Player settings manually and register to download those.

snap has support for muliple channels - edge/beta/stable etc.

We currently push test releases in to edge, so you can swap to that channel if you want to preview forthcoming versions. If issues are spotted there then they don’t make it in to the stable branch, but what I would say is we’ve not experienced the issue you’re reporting at all here to date, so I suspect there’s something environment related at play as well.

Is there any difference btw R3 and R4 with the video files rendering method ?