Chromium-based browser behavior

All, I have recently upgraded my users from RedHat 8 to AlmaLinux 9, and have noticed a strange behavior: Chromium-based browsers will just disappear off the desktop while open and user is utilizing sessions. They use both Google Chrome and Microsoft Edge for Linux–both Chromium-based browsers. This does not occur with Firefox. Most users have Dell Precision 7760 laptops, two have Dell Precision 7750 units. Has anyone seen this type of behavior before?

hello

RHEL 9 uses GNOME Shell on Wayland by default, and X11 applications may run through Xwayland.
Since this issue only affects Chromium-based browsers and not Firefox, I would first test with “GNOME on Xorg” or launch Chrome/Edge with --ozone-platform=x11.

Red Hat documentation:

thanks

Thanks! That’s what I am testing with my users, right now–and even going to have them work with changing their sessions to run Classic X11, if possible, to see if that reduces the behavior.

As of chromium 140 wayland is supported and set as default on chromium, so that should not be relevant.
This sounds more like a gnome shell issue.
But please let us know if forcing x11 actually solves this issue.

Welp, that didn’t help–still getting the occasional disappearing browser (both Chrome and Edge). The only thing that might help is moving to a Wayland-based display manager vs the GNOME 3/X11. Any ideas? Is anyone else experiencing this?

Wayland was the default already in RHEL 8. Therefore, that should not be a new thing.

On login screen (GDM), one should be able to choose session type before typing the password.
The options depend on what is installed. For example:

  • Standard (Wayland) – Gnome
  • Standard (X11) – Gnome
  • Classic (???) – Gnome with different config

If one does choose a non-default session type, then that is remembered and used also on future logins.


I have explicitly disabled Wayland, and have not installed the package that offers Classic (nor any other DE). Hence I have Gnome with Xorg.

I have not noticed Chrome disappearing, nor heard that from other users.
Then again, I do use Chrome only for MS Teams – browsing is with Firefox.


Gnome is that, supposedly already in RHEL 8 (and definitely in RHEL 10, where there is no Xorg).

The “combos” in RHEL 9:

  • Wayland + Gnome
    • Wayland-clients work
    • X11-clients work via XWayland
  • Xorg + Gnome
    • X11-clients work
    • Wayland-clients do not function

An application could support both X11 and Wayland. Then it has to somehow pick which window system it does use. Command-line parameter (as above) or environment variable could be used to force it to use the other window system.

After some time - my boss found out about the conflict between the OpenSC OpenSSL libraries and the Chromium-based browsers, using BoringSSL. We’re going to try and use prlimit in the google-chrome.desktop and microsoft-edge.desktop configurations, to see if that helps. Since Almalinux hasn’t updated the OpenSC package that would mitigate the conflicting modules, this is the decision we’ve made.