You are not logged in.
If I run with
chromium --enable-features=Vulkan --ozone-platform=wayland
, I just get a blank window. I can mouseover it and see the cursor change depending on what's supposed to be highlighted, but no image is produced. There is no console output beyond the message about the cloud management controller. Using nvidia driver 550.54.14 and chromium Chromium 122.0.6261.111 Arch Linux. Also tested with chromium-snapshot-bin Chromium 124.0.6315.0 and brave Brave Browser 122.1.63.169. vkcube works fine. This occurs in either Plasma6 or Hyprland, pointing to either a driver or a Chromium bug.
Separate issue: I got here after troubleshooting why I couldn't get Chromium hw accel to work with ozone-platform=wayland. I found nothing would work until I disabled my iGPU entirely. Prior to that, all Chromium/Electron apps on Wayland would be in non-accelerated mode, with a separate "Hardware GPU" section that showed enabled acceleration options. While acceleration would work under XWayland, it had some weird issues redrawing previous frames, making things like textboxes really annoying to work with (only other thread I found describing that issue is https://forum.cachyos.org/d/451-logseq- … dia-driver). I still haven't tested whether those same issues are present on XWayland with the iGPU off.
I'm running on Plasma 6 with KWIN_DRM_DEVICES set explicitly to the address of the NVIDIA card.
Last edited by cookiecaper (2024-03-12 21:13:06)
Offline
Similar thread:
https://bbs.archlinux.org/viewtopic.php?id=291229
Offline
I am having the same issue with Chromium 124 on the latest Wayland + Nvidia drivers. Basically, the window doesn't render at all.
> sudo pacman -U /var/cache/pacman/pkg/chromium-123.0.6312.122-1-x86_64.pkg.tar.zst
loading packages...
warning: downgrading package chromium (124.0.6367.49-1 => 123.0.6312.122-1)
resolving dependencies...
looking for conflicting packages...
Packages (1) chromium-123.0.6312.122-1
Rolling back at least made it usable.
Last edited by ioquatix (2024-04-14 03:44:37)
Offline
I get same blank window as well after upgrading to chromium 124.0.6367.49-1. I have an nvidia 1660ti but using nouveau drivers
using chromium -ozone-platform-hint=auto opens a blank window and it is using xwayland
I downgraded these packages since they were updated at the same time as chromium but the issue persisted.
xdg-desktop-portal
xorg-server
xorg-server-common
xorg-server-devel
xorg-server-xvfb
Last edited by callmejoe (2024-04-14 06:25:45)
Offline
using chromium -ozone-platform-hint=auto opens a blank window and it is using xwayland
Unrelated to OP who explicitly uses "--ozone-platform=wayland"?
For recent chromium see https://bbs.archlinux.org/viewtopic.php … 3#p2164783
Offline
I get same blank window as well after upgrading to chromium 124.0.6367.49-1. I have an nvidia 1660ti but using nouveau drivers
using chromium -ozone-platform-hint=auto opens a blank window and it is using xwayland
Seems not related to Nvidia. I've got the same issues on Intel iGPU. I set -ozone-platform-hint=auto in flags, and when chromium launches its invisible, except for a psychedelic mouse trace. When checking where its rendered with kwin, it shows its rendered on xWayland. Explicitly launching chromium --ozone-platform=wayland works (thankfully, so i can remove that flag).
I believe I enabled HW rendering with VAAPI, if its relevant.
Offline
Unrelated to OP who explicitly uses "--ozone-platform=wayland"?
For recent chromium see https://bbs.archlinux.org/viewtopic.php … 3#p2164783
ah i totally misread that post. thanks for pointing that out.
and -ozone-platform=wayland solves my issue.
Offline