Nightly does not work with ozone (wayland native)
See original GitHub issueSteps to reproduce
Stable supports running in wayland native like this: element-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland. Doing the same with element-desktop-nightly apparently does not. Maybe because bundles its own electron (assumption based on no dependency in the pkg)?
This is on sway 1.6.1.
What happened?
What did you expect?
element works as usual
What happened?
no window, only the indicator icon appears.
Operating system
arch
Application version
Element Nightly version: 2021090301 Olm version: 3.2.3
How did you install the app?
aur/element-desktop-nightly-bin
Homeserver
own
Have you submitted a rageshake?
No
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Element doesn't work well with native Wayland #18943 - GitHub
I've just tried running Element in native Wayland mode ( --enable-features=UseOzonePlatform --ozone-platform=wayland ) and it seems that currently breaks ...
Read more >Force all apps to use native Wayland : r/Fedora - Reddit
This causes many apps that run on xwayland to be blurry. Is there a way to force every app (most are electron/chromium apps)...
Read more >578890 - [ozone/wayland] Ozone platform for Wayland.
Issue 578890: [ozone/wayland] Ozone platform for Wayland. We can support running chromium on wayland natively by adding a new platform //ui/ozone/platform/ ...
Read more >Chromium - ArchWiki
By default Chromium on Linux does not use any GPU acceleration. ... does not work with the chromium package when using the native...
Read more >Native Wayland Support – Discord
Since Chromium/Electron are starting to get closer to native Wayland ... Discord to run on Wayland no problem using the Ozone build of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Ah, great thanks for the explanation! Let’s assume this is fixed now. Let me know if you ever see this again
It does seem to work in principle now. I’m noticing a last small problem: when running with ozone, the window_properties field is missing. This contains a bunch of meta info to identify the program and is commonly used to e.g. assign apps to fixed workspaces. Consequently my condition that moves windows with class beginning in Element to a certain workspace. get_tree with ozone:
with Xwayland: