[SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

Hakanbaban53 · 2024-05-06 08:16:32

My System Specs:
OS: Arch Linux x86_64
Kernel: 6.8.9-arch1-1
Shell: zsh 5.9
DE: GNOME 46.1
WM: Mutter
CPU: 11th Gen Intel i7-11800H (16) @ 4
GPU: Intel TigerLake-H GT1 [UHD Graphics]
GPU: NVIDIA GeForce RTX 3050 Ti Mobile

When it comes to my issue, whenever I start a Chromium-based browser or any Electron application with the command;

<app_name> --enable-features=UseOzonePlatform --ozone-platform=auto

or

<app_name> --enable-features=UseOzonePlatform --ozone-platform=wayland

the application logo appears in the panel but the window doesn't load And after about 10-20 seconds, the device starts overheating.

Here is my system journal output

I tried in these applications:

Google Chrome Stable(From Aur)
Chromium(Extra)
Microsoft Edge Stable(From Aur)
Discord(Extra)
Visual Studio Code(From Aur)

Last edited by Hakanbaban53 (2024-05-09 06:24:57)

V1del · 2024-05-06 10:53:30

That's a 100MB text file with some kms failures on the nvidia GPU.

Is the nvidia GPU setup for potential wayland support by enabling kms? https://wiki.archlinux.org/title/NVIDIA … de_setting enable nvidia_drm.modeset=1 on the kernel cmdline (modprobe.conf omits a beneficial side effect of killing the simpledrm software device). You will want to do that regardless.

Other than that you might be able to convince the GL loader of the electron apps to not query the nvidia card at all: https://bbs.archlinux.org/viewtopic.php … 7#p2094847

Last edited by V1del (2024-05-06 10:53:56)

Hakanbaban53 · 2024-05-06 12:06:38

V1del wrote:

Is the nvidia GPU setup for potential wayland support by enabling kms? https://wiki.archlinux.org/title/NVIDIA … de_setting enable nvidia_drm.modeset=1 on the kernel cmdline (modprobe.conf omits a beneficial side effect of killing the simpledrm software device). You will want to do that regardless.

I use the nvidia-open-dkms. I didn't make any additional settings other than

sudo ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

When I type

sudo cat /sys/module/nvidia_drm/parameters/modeset

in the terminal, I get the output Y.

seth · 2024-05-06 16:30:45

the application logo appears in the panel but the window doesn't load And after about 10-20 seconds, the device starts overheating

Why? CPU load? By what process? (chromium, gnome/mutter)
Does running chromium on xwayland work? (--ozone-platform=x11)
Do you get xdg-desktop-portal errors in your journal?
Wrt. "100MB" I assume you just posted the entire journal since ever.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

V1del · 2024-05-06 16:31:33

Can you reproduce on the proprietary driver? (Though that has other issues right now, but might avoid this particular specialty)

Hakanbaban53 · 2024-05-06 17:09:30

seth wrote:

Why? CPU load? By what process? (chromium, gnome/mutter)

Chromium is putting a load on the CPU (When I start any Electron application or a Chromium-based browser with Wayland). I haven't noticed any CPU load or instability in Gnome/Mutter.

seth wrote:

Does running chromium on xwayland work? (--ozone-platform=x11)

It's all working properly.

seth wrote:

Why? CPU load? By what process? (chromium, gnome/mutter)

It is a CPU load by chromium (Chromium-based browser or any Electron application I start with wayland.).

seth wrote:

Wrt. "100MB" I assume you just posted the entire journal since ever.
Please post your complete system journal for the boot:

Here

V1del wrote:

Can you reproduce on the proprietary driver? (Though that has other issues right now but might avoid this particular specialty).

I didn't understand exactly what to do. Can you explain in more detail?

Last edited by Hakanbaban53 (2024-05-06 17:13:34)

seth · 2024-05-06 17:25:38

https://archlinux.org/packages/extra/x86_64/nvidia/

But

May 06 19:59:39 Hakan-Arch gnome-shell[2187]: Added device '/dev/dri/card2' (i915) using atomic mode setting.
May 06 19:59:39 Hakan-Arch gnome-shell[2187]: Created gbm renderer for '/dev/dri/card2'
May 06 19:59:39 Hakan-Arch gnome-shell[2187]: Boot VGA GPU /dev/dri/card2 selected as primary

you're running on the intel chip anyway.

May 06 19:59:30 Hakan-Arch kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
May 06 19:59:30 Hakan-Arch kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!) to get rid of the simpledrm device.
The journal only shows MS edge, make sure that actually chromium from the repos is affected and post a journal that *only* covers a failed attempt to run it on the native wayland backend.

Hakanbaban53 · 2024-05-06 20:20:34

Here is the new system journal:
Here

Now, as for what I did:
I added nvidia_drm.modeset=1 to the boot entry parameters Also, I uninstalled nvidia-open-dkms and installed nvidia.
Right now Electron apps and chromium and from what I've seen when I launched their chromium-based browser with wayland, they worked fine.

But what I don't understand is this. Why did I have such a problem with nvidia-open-dkms?

Most likely, I will probably experience the same issue in the next kernel update.

Edit: I didn't have any problems There's probably an issue with the nvidia-open and nvidia-open-dkms packages.

Last edited by Hakanbaban53 (2024-05-09 06:21:08)

seth · 2024-05-06 20:50:18

Feel free to try nvidia-open again.

You should™ not have been running on the nvidia GPU anyway but b/c of the simpledrm device the main device (intel) became card2, nvidia is always card1 and you had no card0 and I'd not be surprised if that ticked electron off…

Hakanbaban53 · 2024-05-06 21:26:49

I just downloaded and tried the nvidia-open package, and I got the same error again.

And now I downloaded and installed the nvidia-dkms package. Currently, Electron applications, Chromium, and Chromium-based browsers have started working on Wayland.

If there is any problem, I will open a new topic and mention it below Thank you for your help ❤️

Arch Linux

#1 2024-05-06 08:16:32

[SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#2 2024-05-06 10:53:30

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#3 2024-05-06 12:06:38

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#4 2024-05-06 16:30:45

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#5 2024-05-06 16:31:33

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#6 2024-05-06 17:09:30

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#7 2024-05-06 17:25:38

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#8 2024-05-06 20:20:34

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#9 2024-05-06 20:50:18

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

#10 2024-05-06 21:26:49

Re: [SOLVED]Electron apps & Chromium-based browsers do not open in Wayland

Board footer