Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`webcord-git`: Not running in Wayland

See original GitHub issue

Aknowledgements

I have checked that there’s no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine.
I have tried running the build from the master branch and it does not have any fixes implemented according to my issue.
My issue describes one of the unstable and/or not fully implemented features.
I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

v19.0.10

Application version

v3.6.0

Bug description

I am running WebCord with the command webcord --ozone-platform=wayland, and it opens as an XWayland window. Is there a way to force it to start in Wayland? I looked at optimize.ts and it appears this command line flag is all that is needed, but it’s either not working or not being picked up. XDG_SESSION_TYPE is set to wayland

Additional context

I am running Arch Linux using the AMD open source drivers on a ROG Zephyrus G14 GA402 laptop, and the Hyprland compositor.

Issue Analytics

State:
Created a year ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

SpacingBat3commented, Sep 30, 2022

OK then, I guess that is going to be expected. You have to specify any Wayland-enabling flag, like --ozone-hint=auto, --ozone-hint=wayland or even the older --ozone-platform=wayland (when running webcord from the CLI or by putting it into appropiate .desktop file). Native Wayland is experimental in WebCord due to upsteam bugs present in Electron and Chromium. From what I know, it has improved greatly over the time, but I still don’t want to force native Wayland because upstream does not treat it as enough stable anyway and it’s better to go back to XWayland in case of the bugs. Just in case, WebCord has its integrations in both XWayland and Wayland, so there should be no much difference between using them at least on that reason.

2reactions

SpacingBat3commented, Aug 8, 2022

Fixed in aur/webcord-git@2e043b1!