GUI Not starting under wayland

Bugs and issues Linux
1

Here is the output of insync start --no-daemon

(I am running SwayWM)

Failed to load client buffer integration: wayland-egl

WARNING:root:While reading /usr/share/applications/mimeapps.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 53, in __index_default_apps
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/mimeapps.list' [line 235]: option 'x-content/video-dvd' in section 'Default Applications' already exists
WARNING:root:While reading /usr/share/applications/mimeapps.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 70, in __index_apps_for_mimetypes
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/mimeapps.list' [line 235]: option 'x-content/video-dvd' in section 'Default Applications' already exists
libpng warning: iCCP: known incorrect sRGB profile
INFO     2020-03-26 09:42:26,947 [mainlogs:_log_run:120] Core(app_version=3.1.1.40765, platform=Linux-x86_64-fedora/31) initialized
WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
qt.qpa.wayland: No shell integration named "xdg-shell" found
qt.qpa.wayland: No shell integration named "xdg-shell-v6" found
qt.qpa.wayland: No shell integration named "wl-shell" found
qt.qpa.wayland: No shell integration named "ivi-shell" found
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells ("xdg-shell", "xdg-shell-v6", "wl-shell", "ivi-shell")
Could not create a shell surface object.
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
INFO     2020-03-26 09:42:27,068 [insync:start_core:44] core started
INFO     2020-03-26 09:42:27,069 [unix_socket_server:start:46] unix socket server thread start
2

Hi @KT_Webster

Can you try running insync show and let me know if this launches the GUI?

3

Even less then insync start I dont even see it run in the status bar:

$ insync show

$ ps aux | grep -i insync

$ karl        3807  0.0  0.0 216116   904 pts/1    S+   09:21   0:00 grep --color=auto -i insync

Does not even want to start with insync show

4

tagging our engineer @Kurt_Ko for further assistance!

5

Ah, dont worry about it. Sway seems to be very buggy. Not using it now and Insync works fine!

1 Like
6

¡Hello! I’m having a similar problem. The GUI works well with Xorg, but when I start session using Wayland, it doesn’t. I’m using Kwin 5.18.5. However, I do see the status bar icon.
Running insync show in a terminal doesn’t give me any output.

7

I need to launch it as insync --qt-qpa-platform=xcb
Launching with insync or insync --qt-qpa-platform=wayland leaves me with no GUI/tray icon.

1 Like
8

I’m still getting no working wayland GUI, and can only get it working when forcing it to use X instead.

Running insync start --no-daemon produces:

`insync start --no-daemon
Failed to load client buffer integration: wayland-egl

INFO 2020-06-17 15:04:30,337 [mainlogs:_log_run:120] Core(app_version=3.1.9.40821, platform=Linux-x86_64-arch/rolling) initialized
INFO 2020-06-17 15:04:30,399 [fswatcher:_start:57] LinuxFSWatcher._start
INFO 2020-06-17 15:04:30,400 [inotify_manager:_pull_loop:312] Inotify loop enter
INFO 2020-06-17 15:04:30,430 [fswatcher:watch:77] watch origin: /home/xxxxxxxxxxxxxxxxxx
INFO 2020-06-17 15:04:30,433 [fswatcher:_start:57] LinuxFSWatcher._start
INFO 2020-06-17 15:04:30,434 [inotify_manager:_pull_loop:312] Inotify loop enter
WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
INFO 2020-06-17 15:04:30,503 [fswatcher:watch:77] watch origin: /home/xxxxxxxxxxxxx
INFO 2020-06-17 15:04:30,515 [insync:start_core:44] core started
INFO 2020-06-17 15:04:30,516 [unix_socket_server:start:46] unix socket server thread start
INFO 2020-06-17 15:04:30,529 [fswatcher:watch:77] watch origin: /home/xxxxxxxxxxxxx
INFO 2020-06-17 15:04:30,555 [fswatcher:watch:77] watch origin: /home/xxxxxxxxxxxxx`

Upon then entering insync show in a separate window, the original process adds:
qt.qpa.wayland: No shell integration named "xdg-shell" found qt.qpa.wayland: No shell integration named "xdg-shell-v6" found qt.qpa.wayland: No shell integration named "wl-shell" found qt.qpa.wayland: No shell integration named "ivi-shell" found qt.qpa.wayland: Loading shell integration failed. qt.qpa.wayland: Attempted to load the following shells ("xdg-shell", "xdg-shell-v6", "wl-shell", "ivi-shell") Could not create a shell surface object. qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

9

This is broken for me as well. This used to work fine under Sway a month or so back. I recently updated both Sway and Insync, and now I have the exact issues cited here.

I can confirm that launching Insync with insync start --qt-qpa-platform=xcb works for me. It would be good if this could play nicely with Wayland/Sway again though.

10

QT supports wayland natively and I have different applications perfectly running with qt-qpa-platform=wayland

I can launch Insync natively under wayland but it is all but consistent…the interface sometimes enters fullscreen mode without window decoration, other times it starts as a very tiny window still without decoration…