Linux release doesn't start on Wayland

[lukateras]

Describe the bug
Beeref v0.2.0 onefile release doesn't start on Wayland due to dependence on a missing key in one of gsettings schemas. Passing GDK_BACKEND=x11 works around the issue (QT_QPA_PLATFORM=xcb, OTOH, doesn't do anything).

Operating system: Fedora Linux 35.20211013.n.0 (Silverblue)
Window system: Wayland

To Reproduce
Steps to reproduce the behavior:

1. Launch BeeRef-0.2.0-linux in a Wayland session.
2. Beeref crashes with SIGTRAP unless GDK_BACKEND=x11 env var is set.

Expected behavior
BeeRef-0.2.0-linux works on Wayland.

Screenshots
Not applicable.

Debug log:

$ ./BeeRef-0.2.0-linux -l TRACE
INFO __main__: Starting BeeRef version 0.2.0
DEBUG __main__: System: Linux durian-dryad 5.14.10-300.fc35.x86_64 #1 SMP Thu Oct 7 20:48:44 UTC 2021 x86_64 x86_64
DEBUG __main__: Python: 3.7.3
INFO __main__: Using settings: /var/home/yana/.config/BeeRef/BeeRef.ini
INFO __main__: Logging to: /var/home/yana/.config/BeeRef/BeeRef.log
GLib-GIO-Message: 20:50:16.775: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(BeeRef-0.2.0-linux:67465): GLib-GIO-ERROR **: 20:50:16.775: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Trace/breakpoint trap (core dumped)

[lukateras]

Output with QT_DEBUG_PLUGINS=1 is no different.

[lukateras]

Beeref.log is essentially empty and is equivalent to the first 5 lines of stdout:

2021-10-27 21:15:14,046 __main__ 68873 139764142349184 Starting BeeRef version 0.2.0
2021-10-27 21:15:14,049 __main__ 68873 139764142349184 System: Linux durian-dryad 5.14.10-300.fc35.x86_64 #1 SMP Thu Oct 7 20:48:44 UTC 2021 x86_64 x86_64
2021-10-27 21:15:14,049 __main__ 68873 139764142349184 Python: 3.7.3
2021-10-27 21:15:14,049 __main__ 68873 139764142349184 Using settings: /var/home/yana/.config/BeeRef/BeeRef.ini
2021-10-27 21:15:14,049 __main__ 68873 139764142349184 Logging to: /var/home/yana/.config/BeeRef/BeeRef.log

[yeahitsjan]

Hey @alpakido,

does starting with --platform wayland or setting QT_QPA_PLATFORM to wayland work out for you?

[lukateras]

Hi! :)

QT_QPA_PLATFORM=wayland ./BeeRef-0.2.0-linux results in the exact same crash as above, and the same output.

It seems that the CLI doesn't accept the --platform flag, so the second approach doesn't work either:

$ ./BeeRef-0.2.0-linux --platform wayland
INFO __main__: Starting BeeRef version 0.2.0
INFO __main__: Using settings: /var/home/yana/.config/BeeRef/BeeRef.ini
INFO __main__: Logging to: /var/home/yana/.config/BeeRef/BeeRef.log
usage: BeeRef-0.2.0-linux [-h] [--settings-dir SETTINGS_DIR]
                          [-l {CRITICAL,FATAL,ERROR,WARN,WARNING,INFO,DEBUG,NOTSET,TRACE}]
                          [--debug-boundingrects] [--debug-shapes]
                          [--debug-handles]
                          [filename]
BeeRef-0.2.0-linux: error: unrecognized arguments: --platform

[lukateras]

I'm guessing this issue is relevant: https://gitlab.gnome.org/GNOME/gtk/-/issues/3680

[rbreu]

I this still an issue? The linked but report has been closed.