Hello, I tested the AppImage packaging on a Debian 4.19.98-1 (2020-01-26) x86_64.
With the Snap version, after a few hours, the player fails. The layout contains only video files.
With AppImage, it’s still running after 1,5days. But there were some errors :
user@LEDO-PLAYER-R17:~/xibo$ ./Xibo_Player-x86_64.AppImage
Setting $XDG_CONFIG_HOME to /home/user/xibo/Xibo_Player-x86_64.AppImage.config
Running in AppImage environment
[11:21:00.331] [1543] [error]: With XInitThreads
(xibo-player:1543): Gdk-ERROR **: 14:47:25.503: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 9645864 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[14:47:28.648] [12462] [error]: With XInitThreads
(xibo-player:12462): Gdk-ERROR **: 19:35:10.004: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 13333127 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[19:35:13.171] [26373] [error]: With XInitThreads
(xibo-player:26373): Gdk-ERROR **: 00:21:53.705: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 13270369 error_code 14 request_code 53 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[00:21:56.878] [7979] [error]: With XInitThreads
Xlib: sequence lost (0x2d0001 > 0x2d0000) in reply type 0x0!
(xibo-player:7979): Gdk-ERROR **: 03:48:32.867: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 8306032 error_code 14 request_code 152 (GLX) minor_code 22)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[03:48:36.007] [18257] [error]: With XInitThreads
(xibo-player:18257): Gdk-ERROR **: 06:56:21.243: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 7715782 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[06:56:24.447] [27655] [error]: With XInitThreads
(xibo-player:27655): Gdk-ERROR **: 11:18:15.653: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 12170319 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[11:18:18.838] [8074] [error]: With XInitThreads
(xibo-player:8074): Gdk-ERROR **: 15:15:09.940: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 11000849 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[15:15:13.080] [19583] [error]: With XInitThreads
Xlib: sequence lost (0x4e0000 > 0x4dffff) in reply type 0x0!
Xlib: sequence lost (0x7a0000 > 0x79ffff) in reply type 0x0!
(xibo-player:19583): Gdk-ERROR **: 18:57:52.274: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 10338146 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[18:57:55.475] [30366] [error]: With XInitThreads
(xibo-player:30366): Gdk-ERROR **: 22:09:08.018: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 8888441 error_code 14 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[22:09:11.168] [7344] [error]: With XInitThreads
(xibo-player:7344): Gdk-ERROR **: 01:30:42.405: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 9134703 error_code 14 request_code 53 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[01:30:45.587] [17177] [error]: With XInitThreads
Xlib: sequence lost (0x1d0007 > 0x1d0006) in reply type 0x0!
Xlib: sequence lost (0x650001 > 0x650000) in reply type 0x0!
(xibo-player:17177): Gdk-ERROR **: 05:30:21.390: The program ‘xibo-player’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadIDChoice (invalid resource ID chosen for this connection)’.
(Details: serial 9297493 error_code 14 request_code 149 (unknown) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Player exited with code 5
[05:30:24.564] [29239] [error]: With XInitThreads
I hope it could help.