We have decided to prepare a release of the Linux Player which fixes 8 issues, shown below. This has been promoted to the latest/candidate and latest/beta channels in Snapcraft.
We have also closed a long running issue #203 which related to errors showing video. It is our opinion that the root cause of this issue was in the snapd environment and has been solved in a Snap update external to Xibo. We have tested with snap 2.47 and no longer experience the issue.
We are still investigating AppImage as an alternative packaging platform, but so far this has brought many more issues than it has solved.
Hi, i have try this version and i try to compile it.
I am sorry but the problem with video is not resolve like you say.
I have error code 11 and 1
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 0# signalStacktraceHandler(int) in /snap/xibo-player/108/bin/player
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 1# 0x00007FF464534FD0 in /lib/x86_64-linux-gnu/libc.so.6
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 2# 0x00007FF456A0E618 in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 3# 0x00007FF456A436DA in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 4# 0x00007FF456A43E28 in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 5# 0x00007FF45670B81D in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 6# 0x00007FF45677619D in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 7# 0x00007FF456AA1046 in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 8# 0x00007FF456701622 in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 9# 0x00007FF45670261C in /var/lib/snapd/lib/gl/libnvidia-glcore.so.340.108
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 10# _attach_renderbuffer at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglframebuffer.c:434
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 11# gst_gl_framebuffer_attach at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglframebuffer.c:473
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 12# gst_gl_framebuffer_new_with_default_depth at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglframebuffer.c:249
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 13# _init_convert_fbo at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglcolorconvert.c:2262
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 14# _init_convert at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglcolorconvert.c:2198
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 15# _do_convert at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglcolorconvert.c:2486
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 16# _gst_gl_context_thread_run_generic at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglcontext.c:1541
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 17# _run_message_sync at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglwindow.c:575
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 18# _run_message_async at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglwindow.c:642
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 19# g_main_context_dispatch in /snap/xibo-player/108/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 20# 0x00007FF46603C650 in /snap/xibo-player/108/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 21# g_main_loop_run in /snap/xibo-player/108/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 22# gst_gl_window_default_run at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglwindow.c:501
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 23# gst_gl_window_run at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglwindow.c:523
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 24# gst_gl_context_create_thread at /build/xibo-player/parts/gst-plugins-base/build/gst-libs/gst/gl/gstglcontext.c:1307
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 25# 0x00007FF466064175 in /snap/xibo-player/108/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 26# start_thread in /lib/x86_64-linux-gnu/libpthread.so.0
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: 27# __clone in /lib/x86_64-linux-gnu/libc.so.6
Dec 10 10:04:07 fst-o-f-xibo2 xibo-player[7831]: Player exited with code 11
Dec 10 10:04:10 fst-o-f-xibo2 xibo-player[7831]: [10:04:10.675] [8667] [error]: [DBus] ScreenSaver wont'be suspended: org.freedesktop.DBus.Error.Spawn.ExecFailed
Dec 10 10:04:11 fst-o-f-xibo2 player[8667]: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Dec 10 10:04:49 fst-o-f-xibo2 player[8667]: player: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Dec 10 10:04:49 fst-o-f-xibo2 xibo-player[7831]: Player exited with code 1
Dec 10 10:04:53 fst-o-f-xibo2 xibo-player[7831]: [10:04:53.057] [8761] [error]: [DBus] ScreenSaver wont'be suspended: org.freedesktop.DBus.Error.Spawn.ExecFailed
Dec 10 10:04:53 fst-o-f-xibo2 player[8761]: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Dec 10 10:05:16 fst-o-f-xibo2 player[8761]: player: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Dec 10 10:05:16 fst-o-f-xibo2 xibo-player[7831]: Player exited with code 1
Dec 10 10:05:19 fst-o-f-xibo2 xibo-player[7831]: [10:05:19.257] [8831] [error]: [DBus] ScreenSaver wont'be suspended: org.freedesktop.DBus.Error.Spawn.ExecFailed
Dec 10 10:05:19 fst-o-f-xibo2 player[8831]: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
my conf :
snap 2.48.1
snapd 2.48.1
series 16
ubuntu 18.04
kernel 4.15.0-122-generic
What do you mean by trying to compile it? It has a very specific build process and unless you have a reason to compile it, it would be better to run the snap. I actually think you are running the snap looking at your logs.
I don’t think the errors you’ve got there are the same as the previous issue, but I will forward on to the developers for them to look at.
Thanks to answer. Maybe i don’t used to good process, i building manually the snap, for one reason :
i don’t want my player are update without i know that, at this moment i have 10 players who doesn’t work because the video playback are not stable. That’s why i decide to do it.
I have realise a fresh install on a dell optiplex 9020 with intel chipset and it’s works. But on my lab pc (dell optiplex 760 with nvidia 9300GE) it doesn’t work anymore… (Player exited with code 11 and code 1).
With AppImage it’s works on this configuration.
Edit : I have change my nvidia 9300GE by ati 6450 and it’s works… So my old Nvidia card doesn’t work anymore with this version
I totally understand - but I don’t think that building your own snap from source actually solves that problem for you. The video playback issue has come about without any updates to the snap package from our side - it is something in the OS/snap itself that has changed.
That being said, if you want to build from source, and follow the instructions, then in theory you should get the exact same package as we do.
Yes you are right.
But build my own snap is great for to manage my player version, because when you have xx player who stop to work because snap was updated automaticly, people want to kill me
That 's why for the futur version i will build my snap just for that. (i woul prefer AppImage but for the moment you prefer to use snap)
We are making sure we release much slower through edge, beta, candidate before publishing to stable. It might also be useful to read this document about how to control snap updates: https://snapcraft.io/docs/keeping-snaps-up-to-date
However ultimately if you want to build your own snap, then sure
Your report above is still with the development team, so I will let you know when I have a response.
If the AppImage we’ve released works for you, then by all means use it. We haven’t completely ruled it out, just temporarily stopped to get a release out.
