Sioyek does not start

[FliiFe]

No window ever opens. I'm using plasma on wayland, with an nvidia graphics card using the official driver and up to date mesa (see below for version info).

Note that this bug does NOT appear when running on the same computer with the same configuration but with plasma on x11.

Also, the logs below are from the development branch, but the same issue was present with the main branch.

QEGLPlatformContext: Failed to create context: 3009
Warning: fallback to QtQuick software backend.
QEGLPlatformContext: Failed to create context: 3009
default_config_path: /opt/sioyek/prefs.config
Error: default_config_path: /opt/sioyek/prefs.config doesn't exist!
default_keys_path: /opt/sioyek/keys.config
Error: default_keys_path: /opt/sioyek/keys.config doesn't exist!
user_config_path: [ 0 ] /etc/xdg/sioyek/prefs_user.config
user_config_path: [ 1 ] /home/tjbc/.config/kdedefaults/sioyek/prefs_user.config
user_config_path: [ 2 ] /home/tjbc/.config/sioyek/prefs_user.config
user_config_path: [ 3 ] /home/tjbc/.local/share/Sioyek/prefs_user.config
user_config_path: [ 4 ] /home/tjbc/.config/sioyek/prefs_user.config
user_keys_path: [ 0 ] /etc/xdg/sioyek/keys_user.config
user_keys_path: [ 1 ] /home/tjbc/.config/kdedefaults/sioyek/keys_user.config
user_keys_path: [ 2 ] /home/tjbc/.config/sioyek/keys_user.config
user_keys_path: [ 3 ] /home/tjbc/.local/share/Sioyek/keys_user.config
user_keys_path: [ 4 ] /home/tjbc/.config/sioyek/keys_user.config
database_file_path: /home/tjbc/.local/share/Sioyek/test.db
local_database_file_path: /home/tjbc/.local/share/Sioyek/local.db
global_database_file_path: /home/tjbc/.local/share/Sioyek/shared.db
tutorial_path: /home/tjbc/.local/share/Sioyek/tutorial.pdf
last_opened_file_address_path: /home/tjbc/.local/share/Sioyek/last_document_path.txt
shader_path: /opt/sioyek/shaders
SIOYEK
QEGLPlatformContext: Failed to create context: 3009
QRhiGles2: Failed to create temporary context
QEGLPlatformContext: Failed to create context: 3009
QRhiGles2: Failed to create context
Failed to create QRhi for QBackingStoreRhiSupport
QEGLPlatformContext: Failed to create context: 3009
QOpenGLWidget: Failed to create context
warning: found duplicate fz_icc_link in the store
QEGLPlatformContext: Failed to create context: 3009
QOpenGLWidget: Failed to create context
QEGLPlatformContext: Failed to create context: 3009
QOpenGLWidget: Failed to create context
QEGLPlatformContext: Failed to create context: 3009
QOpenGLWidget: Failed to create context

$ glxinfo | grep version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.6.0 NVIDIA 550.142
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 550.142
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 550.142
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    GL_EXT_shader_group_vote, GL_EXT_shader_implicit_conversions,

mesa was compiled with nvidia and zink support.

[ahrm]

Does this help: #1128 (comment) ?

[FliiFe]

It doesn't. I've tried to unset WAYLAND_DISPLAY too, and I've also tried MESA_GL_VERSION_OVERRIDE=3.2 MESA_GLSL_VERSION_OVERRIDE=320 which was suggested in another issue. None had any effect.

[ahrm]

I unfortunately don't have a wayland machine to test it right now, maybe someone else with wayland can help?

[KorigamiK]

This may be because you are using the app image version (is that correct?). Perhaps you should be running it though xwayland and try instead.

Try setting the following env variable for this

QT_QPA_PLATFORM=xcb sioyek

You should also provide details on how you are building the binary

[FliiFe]

Using this environment variable did indeed work. I am not using an AppImage. The binary was build via this ebuild.

[FliiFe]

I haven't tested on X11 yet but it seems launching this way prevents sioyek from recognising keyboard inputs. In the logs:

Warning: invalid command (key:8); resetting to root
Warning: invalid command (key:9); resetting to root
Warning: invalid command (key:9); resetting to root
Warning: invalid command (key:9); resetting to root
Warning: invalid command (key:8); resetting to root
Warning: invalid command (key:8); resetting to root
Warning: invalid command (key:q); resetting to root
Warning: invalid command (key::); resetting to root
Warning: invalid command (key:/); resetting to root
Warning: invalid command (key:); resetting to root
Warning: invalid command (key:); resetting to root
Warning: invalid command (key::); resetting to root
Warning: invalid command (key:t); resetting to root
Warning: invalid command (key:i); resetting to root
Warning: invalid command (key:o); resetting to root
Warning: invalid command (key:s); resetting to root
Warning: invalid command (key:d); resetting to root
Warning: invalid command (key:o); resetting to root
Warning: invalid command (key:f); resetting to root
Warning: invalid command (key:s); resetting to root
Warning: invalid command (key:o); resetting to root
Warning: invalid command (key:d); resetting to root
Warning: invalid command (key:g); resetting to root

If I can reproduce under X11 i'll open a new issue for this.

[ahrm]

Are the keys.config and prefs.config file next to the executable?

[FliiFe]

Here are the files installed:

$ equery files sioyek
 * Searching for sioyek ...
 * Contents of app-text/sioyek-9999:
/opt
/opt/sioyek
/opt/sioyek/shaders
/opt/sioyek/shaders/compiled_drawing.vertex
/opt/sioyek/shaders/compiled_line.fragment
/opt/sioyek/shaders/custom_colors.fragment
/opt/sioyek/shaders/dark_mode.fragment
/opt/sioyek/shaders/debug.fragment
/opt/sioyek/shaders/dot.fragment
/opt/sioyek/shaders/dot.vertex
/opt/sioyek/shaders/highlight.fragment
/opt/sioyek/shaders/line.fragment
/opt/sioyek/shaders/line.vertex
/opt/sioyek/shaders/separator.fragment
/opt/sioyek/shaders/simple.fragment
/opt/sioyek/shaders/simple.vertex
/opt/sioyek/shaders/simple_transparent.fragment
/opt/sioyek/shaders/stencil.fragment
/opt/sioyek/shaders/stencil.vertex
/opt/sioyek/shaders/undendered_page.fragment
/opt/sioyek/shaders/unrendered_page.fragment
/opt/sioyek/shaders/vertical_bar.fragment
/opt/sioyek/shaders/vertical_bar_dark.fragment
/opt/sioyek/sioyek
/usr
/usr/share
/usr/share/applications
/usr/share/applications/sioyek.desktop
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/sioyek.1.bz2
/usr/share/pixmaps
/usr/share/pixmaps/sioyek-icon-linux.png
/usr/share/sioyek
/usr/share/sioyek/keys.config
/usr/share/sioyek/prefs.config
/usr/share/sioyek/tutorial.pdf

You're right though that sioyek is looking besides its binary

default_config_path: /opt/sioyek/prefs.config
Error: default_config_path: /opt/sioyek/prefs.config doesn't exist!
default_keys_path: /opt/sioyek/keys.config
Error: default_keys_path: /opt/sioyek/keys.config doesn't exist!

[FliiFe]

Coming back to the original issue: sioyek flickers hard when launched with xwayland. This is a similar kind of flickering to that of gpu-accelerated electron applications.