Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Armcord tries to use X11 when using Wayland [Plasma 6] #549

Open
erictelkkala opened this issue Feb 5, 2024 · 3 comments
Open

Armcord tries to use X11 when using Wayland [Plasma 6] #549

erictelkkala opened this issue Feb 5, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@erictelkkala
Copy link

Describe the bug
When using Wayland, and starting Flatpak Armcord, it tries to use X11 session-bus, but cannot find it.

To Reproduce
Steps to reproduce the behavior:

  1. Use Plasma 6?
  2. Use X11
  3. Log out and switch to Wayland
  4. See error

Expected behavior
Should start

Log

flatpak run xyz.armcord.ArmCord 
Using Wayland, enabling PipeWire for video capture.
Screenshare may be broken on first start.
Make sure you have the legacy screencapturer enabled.
Wayland socket not available, running through Xwayland.
Using NVIDIA on Wayland, applying workaround
Passing the following arguments to Electron: --enable-gpu-rasterization --enable-zero-copy --enable-gpu-compositing --enable-native-gpu-memory-buffers --enable-oop-rasterization --disable-gpu-blocklist --disable-gpu-sandbox --enable-features=UseSkiaRenderer,WebRTCPipeWireCapturer,WebRTCPipeWireCapturer
[3:0205/195336.053726:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Config is fine
Window config is fine
Wayland detected, using PipeWire for video capture.
[Config manager] doneSetup: true
[Config manager] performanceMode: none
ArmCord has been run before. Skipping setup.
No performance modes set
[Config manager] windowStyle: default
[3:0205/195336.166980:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
[3:0205/195336.166987:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
[0205/195336.169285:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
/app/bin/startarmcord: line 39:     3 Segmentation fault      (core dumped) zypak-wrapper /app/bin/armcord/armcord "${FLAGS[@]}" "$@"

Desktop (please complete the following information):

  • OS: openSUSE Tumbleweed x86_64
  • Method of installation: Flatpak
  • Version 3.2.6 - Stable

Additional context

  • Kernel: 6.7.2-1-default
  • DE: Plasma 6.0.80
  • WM: kwin
@erictelkkala erictelkkala added the bug Something isn't working label Feb 5, 2024
@IsaacMarovitz
Copy link

Same issue on Fedora 39 Asahi Linux Remix

@a-plastic-bag
Copy link

a-plastic-bag commented Mar 29, 2024

Also experiencing this on Fedora 39 Asahi Remix on Gnome 45. ArmCord runs, but only through X11. Attempting to force it to use Wayland with --ozone-platform=wayland makes it segfault with the following output. This only happens with the Flatpak version. The error does seem to be a bit different to the one above:

Using Wayland, enabling PipeWire for video capture.
Screenshare may be broken on first start.
Make sure you have the legacy screencapturer enabled.
Wayland socket not available, running through Xwayland.
Passing the following arguments to Electron: --enable-gpu-rasterization --enable-zero-copy --enable-gpu-compositing --enable-native-gpu-memory-buffers --enable-oop-rasterization --disable-gpu-blocklist --enable-features=UseSkiaRenderer,WebRTCPipeWireCapturer,WebRTCPipeWireCapturer
[3:0329/181116.342698:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Config is fine
Window config is fine
Wayland detected, using PipeWire for video capture.
[Config manager] doneSetup: true
[Config manager] performanceMode: none
ArmCord has been run before. Skipping setup.
No performance modes set
[Config manager] windowStyle: default
[3:0329/181116.435778:ERROR:wayland_connection.cc(193)] Failed to connect to Wayland display: No such file or directory (2)
[3:0329/181116.435788:ERROR:ozone_platform_wayland.cc(259)] Failed to initialize Wayland platform
[3:0329/181116.435791:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
[0329/181116.437011:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
/app/bin/startarmcord: line 39:     3 Segmentation fault      (core dumped) zypak-wrapper /app/bin/armcord/armcord "${FLAGS[@]}" "$@"

Side note: I've noticed that when using the normal version of armcord with --ozone-platform=wayland, the command --disable-features=WaylandFractionalScaleV1 doesn't work. Is this because ArmCord uses an old version of Electron that doesn't let you disable that? Without disabling it, Wayland Electron/Chromium apps appear blurry on Gnome.

@QazCetelic
Copy link

I'm also experiencing this issue on OpenSUSE with Armcord 3.2.6.

Screenshare may be broken on first start.
Make sure you have the legacy screencapturer enabled.
Wayland socket not available, running through Xwayland.
Passing the following arguments to Electron: --enable-gpu-rasterization --enable-zero-copy --enable-gpu-compositing --enable-native-gpu-memory-buffers --enable-oop-rasterization --disable-gpu-blocklist --enable-features=UseSkiaRenderer,WebRTCPipeWireCapturer,WebRTCPipeWireCapturer
[3 zypak-helper] Wait found events, but sd-event found none
[3:0411/112416.039129:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Config is fine
Window config is fine
[Config manager] multiInstance: false
[3:0411/112416.177429:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0411/112416.177465:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[Config manager] armcordCSP: true
[Config manager] doneSetup: true
Setting up CSP unstricter...
[Config manager] trayIcon: ac_white_plug
[Config manager] trayIcon: ac_white_plug
[Config manager] tray: true
[Config manager] clientName: ArmCord

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants