Okay, let's just talk only about the large text text then. Wayland ------------- Ubuntu -> Settings -> accessibility -> seeing -> large text. Chromium's v127.0.6533.119. The interface does not change at all. But it must change.
** Attachment added: "Screenshot from 2024-08-19 12-25-16.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+attachment/5806970/+files/Screenshot%20from%202024-08-19%2012-25-16.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Difference in behavior in wayland and xorg sessions Status in chromium-browser package in Ubuntu: New Bug description: Chromium - 127.0.6533.119 wayland Chromium app ignores large text setting There is no top bar named New Tab - chromuim ------------------------------------------------------------- xorg There is top bar named New Tab - chromuim There is a bug "Chromium opens, but still loads within 15 seconds after opening" ------------------------------------------------------------- What needs to be done: 1)Remove top bar in xorg session. The flatpak or aur version does not have this top bar. It should not be in any session. Moreover, Google Chrome deb version comes without a top bar. 2)Chromium app should not ignore large text setting in ubuntu in wayland session 3)Chromium opens, but still loads within 15 seconds after opening https://issues.chromium.org/issues/349835592 https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889 It seems someone has created a custom patch for the Wayland session within the Snap format. Chromium now launches directly into the Wayland session without any delay. As seen in the upstream bug, no one seems to know why this is happening or is willing to address it. In other words, Google doesn't seem to prioritize Linux development. We need to figure out what this patch does, how to integrate it into the xorg session, and who can merge it into the upstream repository. This is a serious issue affecting all GNOME-based and chromium-based browser distributions and their forks, and it's being ignored. ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 18 20:25:21 2024 InstallationDate: Installed on 2024-08-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> Snap: chromium 127.0.6533.119 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
