Adobe-Connect-Linux icon indicating copy to clipboard operation
Adobe-Connect-Linux copied to clipboard

Running under Wayland

Open MJKhaani opened this issue 1 year ago • 1 comments

Describe the bug Hi and thanks for your efforts.

I was using your app under Wayland (Hyprland WM) and it worked flawlessly. But affter some updates (Don't know witch one) the app starts and will slow the whole system and stuck before loading.

[0831/184923.865125:INFO:cpu_info.cc(53)] Available number of cores: 16
[0831/184923.865126:INFO:cpu_info.cc(53)] Available number of cores: 16
[0831/184923.865172:VERBOSE1:zygote_main_linux.cc(218)] ZygoteMain: initializing 0 fork delegates
[0831/184923.865172:VERBOSE1:zygote_main_linux.cc(218)] ZygoteMain: initializing 0 fork delegates
[0831/184923.898856:VERBOSE1:pref_proxy_config_tracker_impl.cc(186)] 0x55d64486dcd0: set chrome proxy config service to 0x55d64481ab00
[0831/184923.901006:VERBOSE1:webrtc_internals.cc(118)] Could not get the download directory.

DevTools listening on ws://127.0.0.1:9450/devtools/browser/9f4572d0-7ede-4fdb-afa9-4dc6c52f1718
[0831/184923.904357:VERBOSE1:pref_proxy_config_tracker_impl.cc(186)] 0x55d6449d8ca0: set chrome proxy config service to 0x55d6449d90f0
[0831/184923.943694:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  15 (X_QueryTree)
  Resource id in failed request:  0x1a00001
  Serial number of failed request:  40100
  Current serial number in output stream:  40100

If you can fix it I'll be grateful.

  • Distro: Arch Linux
  • Kernel: 6.4.12-arch1-1
  • Window Manager: hyprland 0.28.0-1

MJKhaani avatar Aug 31 '23 15:08 MJKhaani

I see where this is coming from. The project relies on Xlib and isn't natively compatible with Wayland. This can be fixed, but I don't have the time for it as of right now (I'm just a busy high schooler!). I suggest if the issue makes the app/system unusable and is a necessity for you, temporarily switch to Xorg or downgrade whatever update caused this until I find the time to fix it

mahancoder avatar Sep 01 '23 16:09 mahancoder