Chromium wayland

Those using the Chromium web browser on Ubuntu by way of the Snap package, the latest build has now enabled (optional) Wayland support.There has long been X11 and Wayland Ozone support available in various testing forms. However, enabling the experimental native Wayland support with Ubuntu's Chromium Snap hasn't been possible since that build force-disables the Wayland support.Going back to 2020 there has been this Ubuntu chromium-browser bug report over Chromium's Wayland support being disabled with the "DISABLE_WAYLAND" option.That bug report discussion was restarted in March and now with the latest Chromium snap builds, the one line change has landed so the DISABLE_WAYLAND support isn't set and therefore forcing the Wayland support code in Ozone to not be built.By default the Chromium browser Snap on Ubuntu will still default to X11/XWayland, but at least it now allows for run-time opting over to using the native Wayland code path if so desired.Those running the Chromium Snap builds within the past week can adjust your default preference via chrome://flags/#ozone-platform-hint if wanting to use the web browser's native Wayland code.

Wayland News Archives938 Wayland open-source and Linux related news articles on Phoronix since 2008. Niri 25.02 & Labwc 0.8.3 Wayland Compositors Released The Niri and Labwc Wayland compositor projects are both out with new releases this weekend to further their efforts. 22 February 2025 - Niri + Labwc Releases SDL & MPV Media Player Land Support For Wayland Color Management / HDR Following the upstream Wayland Protocols repository landing the Wayland color management protocol for enabling HDR support and this morning's release of Wayland Protocols 1.41, the SDL library and MPV media player are the first two clients supporting this now-official protocol. 17 February 2025 - MPV Media Player + SDL Library Wayland Protocols 1.41 Released With Color Management Support Wayland Protocols 1.41 is shipping today with the color management protocol added for enabling high dynamic range (HDR) support on the Wayland-powered Linux desktop. 17 February 2025 - Wayland Protocols 1.41 Wayland Color Management & HDR Protocol Support Merged As a quick follow-up to the article earlier today... The Wayland Color Management and HDR protocol support is now merged to upstream Wayland Protocols! 13 February 2025 - Wayland HDR! Wayland Color Management & HDR Protocols Expected To Be Merged Imminently Today could finally be the day. In the works for 5+ years, the Wayland color management and HDR protocol additions look like they will finally be merged in the coming hours. 13 February 2025 - Today, Today, Todau Chromium Embedded Framework "CEF" Seeing Progress On Wayland Support One of the important pieces of open-source software still working toward proper Wayland support is the Chromium Embedded Framework "CEF" that in turn is depended upon by software like Steam, OBS Studio, Spotify, and many other software packages for having an in-app browser-type experience. The good news is there has been some recent progress on native Wayland support for CEF. 31 January 2025 - CEF On Wayland Hyprland 0.47 Wayland Compositor Delivers Experimental HDR, GPU Hotplugging Hyprland 0.47 is out to begin a new week with some exciting enhancements to this visuals-focused Wayland compositor. 27 January 2025 - Hyprland 0.47 Hyprland Wayland Compositor Lands HDR / Color Management Support Hyprland is now the latest Wayland compositor supporting the color management protocols and allowing High Dynamic Range (HDR) color support with capable displays. 13 January 2025 - Hyprland Goes HDR Niri 25.01 Scrollable-Tiling Wayland Compositor Brings More Features Niri 25.01 was released on Saturday

DBus- Updated Chromium to 128.0.6613.178- Updated Node.js to v20.18.0Electron 32.1.2 (64-bit)Fixed:- Fixed an issue where clicking the eyedropper icon did nothing instead of opening an eyedropper for color selection as expected- Third time isn't always a charm. Fixed the native macOS Screen Share picker invocation triggering a test Chromium green screenElectron 32.1.1 (64-bit)Fixed:- Fixed an issue when dragging to resize when using Window Controls Overlay on Linux- Fixed an issue where WebContentsViews did not show correctly in some circumstances on macOS after being added as child viewsOther Changes:- Updated Chromium to 128.0.6613.137Electron 32.1.0 (64-bit)Features:- Added support for the macOS system picker in desktopCapturer and setDisplayMediaRequestHandlerFixed:- Fixed BrowserView auto resize issue- Fixed a potential issue with fillable PDF forms saving correctly in some circumstances- Fixed an issue where defaultPath did not work for all users on Linux when creating an open file dialog- Fixed an issue where users would be incorrectly notified of print failure upon intentional cancellation- Fixed an issue with resize events being emitted on Windows when the window was moved but not resized- Fixed other apps not being focused when launched from electron ozone/wayland- Restored Chromium default Content-Disposition header parsingOther Changes:- Updated Chromium to 128.0.6613.120- Updated Node.js to v20.17.0Electron 32.0.2 (64-bit)Fixed:- MenuItem.click handler not setting focusedWindow parameter when focused window is a BaseWindow- an issue where BaseWindow.setTouchBar didn't work as expected- bug where camera permissions affected screen sharing- devtools to allow restoring saved dock state on Linux when WCO is enabled- electron app in ozone/wayland not being focused when launched from another appOther Changes:- Updated Chromium to 128.0.6613.84Electron 32.0.0 (64-bit)Features:- Added support for responding to auth requests initiated from utility process via app#login event- Enabled zstd compression in net http requestsOther Changes:- Updated Chromium to 128.0.6613.36Electron 31.4.0 (64-bit)Features:- Added a new property prefersReducedTransparency to nativeTheme, which indicates whether the user has chosen to reduce OS-level transparency via system accessibility settingsFixed:- Fixed a crash that could occur in some DevTools extensions containing draggable regions- Fixed an issue where navigator.serial.getPorts() incorrectly returned an empty array in some cases- Fixed an issue where system-context-menu was not triggered as expected on Windows

导读：我们能否在 Arch Linux 中通过主流的桌面环境或窗口管理器来全面运行 Wayland？一起来探索答案。 本文字数：4997，阅读时长大约： 7分钟 Arch Linux 中通过主流的桌面环境或窗口管理器来全面运行 Wayland？一起来探索答案。Wayland 是一种针对 Linux 运行图形应用的高效、现代化的协议。相较之下，它在安全、稳定和图形性能方面相较老旧的 X.Org 显示服务器表现更出色。尽管 X.Org 多年来一直是默认的显示服务器，但其年代漫长且复杂度高，导致了许多问题，包括安全漏洞和对新型硬件的兼容性问题。而 Wayland 提供了一个更简洁和安全的显示协议，用以解决这些问题。虽然向 Wayland 转型已经有近十年的时间，但这是可以理解的。大型 Linux 发行版，例如 Ubuntu 和 Fedora，自 2021 年起就默认使用 Wayland，因为该协议现已逐渐稳定。然而，对 Arch Linux 用户来说，使用 Wayland 进行自定义安装可能会比较复杂。在所有主流桌面环境中，只有 KDE Plasma 和 GNOME 有最新的 Wayland 支持。Xfce、LXQt 及其他桌面环境正在开发支持 Wayland 的功能，但现在还没有做好准备。在窗口管理器方面，Sway 在 Arch Linux 中已经全面支持 Wayland。尽管如此，我还是希望能测试 Wayland 在 Arch 中的表现，并给你提供一个截至今日的状态报告。让我们来尝试在 Arch Linux 中配置 KDE Plasma 和 GNOME 以全面支持 Wayland。Arch Linux 中的 Wayland 设置在理想的情况下，你应已经安装了 archlinux.org。打开一个终端，并通过运行下列命令进行核实： pacman -Qi wayland如果你尚未安装，则可以使用以下命令进行安装： sudo pacman -S --needed waylandKDE Plasma 桌面环境接下来的步骤设定的前提条件是你拥有一个没有安装任何桌面环境或窗口管理器的裸机 Arch Linux 环境。你可以通过使用 www.debugpoint.com 进行 Arch Linux 的裸机安装。在 Arch Linux 中，为了设置标准的 KDE Plasma，我们需要对 Wayland 进行一些调整。因此，该过程中需要从 AUR 安装一些包进来，这就要求你已经 www.debugpoint.com 或者其他的 AUR 辅助工具。首先，利用以下命令从 AUR 安装一个定制的 sddm 显示管理器 Wayland 软件包。请注意，这个 sddm 包与 Arch Extra 仓库中的 sddm 包并不相同。根据 wiki.archlinux.org 的指南，只有 GDM 和 sddm-git 在 Arch Linux 中提供了完善的 Wayland 支持。 yay -S sddm-git安装完成后，执行下述命令来安装更多 Wayland 包。 ◈ xorg-xwayland：使得 xclients 能在 Wayland 下运行 ◈ xorg-xlsclients：列出正在一个显示端口上运行的客户端应用（可选） ◈ qt5-wayland：为 Wayland 提供的 Qt API ◈ glfw-wayland：供 Wayland 使用的 GUI 应用开发包 pacman -S --needed xorg-xwayland xorg-xlsclients qt5-wayland glfw-wayland然后，执行以下命令以安装 Plasma 和与 Wayland 会话关联的应用。请保持以下的安装顺序。 pacman -S --needed plasma kde-applications pacman -S --needed plasma-wayland-session注意：如果你是英伟达用户，你可能需要考虑安装 egl-wayland 包，但需要说明的是，我没有尝试过此操作。我们现在来安装 Firefox 和 Chromium，这样能够帮助我们测试 Wayland 是否正常运行。 pacman -S --needed firefox chromium安装完成后，启动 sddm 显示管理器和 NetworkManager 服务。 sudo systemctl enable sddm sudo systemctl enable NetworkManager另外，sddm 显示管理器需要做一些额外设置。使用你喜欢的文本编辑器，打开 sddm 的配置文件，然后在 [Theme] 下面添加 Current=breeze。 sudo nano /usr/lib/sddm/sddm.conf.d/default.conf [Theme] # current theme name Current=breeze设置完成后，保存并关闭文件，然后进行重启。 reboot重启后，在登录屏幕上，你应该可以看到 Wayland 的选项。选择并登录 KDE Plasma 的 Wayland 会话。Plasma Wayland 会话登录界面你还能通过查看 $XDG_SESSION_TYPE 变量来 www.debugpoint.com。Arch Linux 中运行的 KDE Plasma 与 Wayland如果你希望强制让 Firefox 以 Wayland 运行，那么就在 /etc/environment 中添加以下行。 MOZ_ENABLE_WAYLAND=1然后重新启动或执行下方的命令使其生效。 source /etc/environment打开 Firefox，进入 about:support 页面来校验 “Window protocol” 的值。你也可以通过在终端中运行 xlsclients 来查看哪些外部应用正在运行在 Wayland 下。在 Arch 和 KDE Plasma 下 Firefox 使用的是 xwayland至此，你已经完成了在 Arch Linux 中使用 Wayland 安装配置 KDE Plasma 的全部步骤。Wayland KDE Plasma 在 Arch 中的性能表现总体而言，Arch Linux 下的 KDE Plasma 配合 Wayland 运行得相当顺畅，未出现任何中断使用或重大问题的情形。截图和屏幕录制应用 Spectacle 功能一切正常。尽管如此，我在测试过程中还是注意到了几个小问题。首先，在开启如 Dolphin 这类应用程序时，底部面板时不时会出现闪烁，这主要是在 VirtualBox 会话中观察到的。其次，鼠标指针的变化行为有点奇怪。它无法适時地从指针状态切换到操作手柄状态（详见下图）。最后，当从待机/屏幕关闭状态恢复在线时（在没有安装客户机插件的 VirtualBox 中），KWin 会崩溃。虽然这可能只是虚拟机特有的现象，但仍然需要进行硬重启才能返回到桌面。在 Arch Linux 的 Wayland 会话闲置状态下，内存消耗大约为 2GB。GNOME在 Arch Linux 中，GDM 显示管理器已经完全支持 Wayland。首先，我们通过下列命令安装 GDM： pacman -S --needed gdm安装完毕后，使用以下命令安装几个 Wayland 需要的包。 ◈ xorg-xwayland：使得 xclients 能在 Wayland 下运行 ◈ xorg-xlsclients：用于列出在显示器上运行的应用程序（可选） ◈ glfw-wayland：Wayland 的图形用户界面应用开发包 pacman -S --needed xorg-xwayland xorg-xlsclients glfw-wayland接下来，你可以用下面的一系列命令来安装 GNOME 和一些与 Wayland 会话相关的应用。请确保按照下列给出的顺序来执行这些命令。 sudo pacman -S --needed gnome gnome-tweaks nautilus-sendto gnome-nettool gnome-usage gnome-multi-writer adwaita-icon-theme xdg-user-dirs-gtk fwupd arc-gtk-theme注意：如果你正在使用英伟达，你可能需要安装 egl-wayland 软件包，但我并未亲自试过此方法。接下来，我们还要安装 Firefox 和 Chromium，这样你就能测试 Wayland 是否在 GNOME 中正常运行。 pacman -S --needed firefox chromium一旦这项任务完成，就启动 GDM