Arch Linux

ArchUser2025

Member

Registered: 2025-05-01

Posts: 11

[solved?] chromium and glycin

After updating chromium to version 140.0.7339.207-1, I see new processes when starting the browser.

└─ /usr/bin/sway ...
   └─ /usr/lib/chromium/chromium ...
      ├─ ...
      ├─ bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --learenv -setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run ... --symlink /usr/lib /lib64 --symlink /usr/lib /lib --seccomp 349 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 348
      │  └─ bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv --setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run ... --symlink /usr/lib /lib64 --symlink /usr/lib /lib --seccomp 349 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 348
      │     └─ /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 348
      └─ bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv --setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run ... --symlink /usr/lib /lib64 --symlink /usr/lib /lib --ro-bind-try /etc/fonts/conf.d /etc/fonts /conf.d --ro-bind-try /etc/fonts/fonts.conf /etc/fonts/fonts.conf ... --seccomp 341 /usr/lib/glycin-loaders/2+/glycin-svg --dbus-fd 339
         └─ bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv --setenv HOME /tmp-home --setenv XDG_RUNTIME_DIR /tmp-run ... --symlink /usr/lib /lib64 --symlink /usr/lib /lib --ro-bind-try /etc/fonts/conf.d /etc/fonts/conf.d --ro-bind-try /etc/fonts/fonts.conf /etc/fonts/fonts.conf ...--seccomp 341 /usr/lib/glycin-loaders/2+/glycin-svg --dbus-fd 339
            └─ /usr/lib/glycin-loaders/2+/glycin-svg --dbus-fd 339

It looks a bit strange and inappropriate. I don't have /nix/store, /tmp-home and /tmp-run.
Is that how it should be? Or do I need to configure chromium/bubblewrap/gdk-pixbuf/glycin somehow?
I've seen some news . Will the browser work correctly now if I have a kernel parameter  `kernel.unprivileged_userns_clone = 0 `?

Last edited by ArchUser2025 (2025-09-26 19:13:38)

tekstryder

Member

Registered: 2013-02-14

Posts: 504

Re: [solved?] chromium and glycin

See: https://bbs.archlinux.org/viewtopic.php?id=308456

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,690

Re: [solved?] chromium and glycin

Will the browser work correctly now if I have a kernel parameter  `kernel.unprivileged_userns_clone = 0 `?

Not likely, but you could also just try.
The leaking bwrap processes are a bug, see https://bbs.archlinux.org/viewtopic.php?id=308467 and the wiki paragraph you linked - the general glycin/bwrap situation is by de*sigh*n.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ArchUser2025

Member

Registered: 2025-05-01

Posts: 11

Re: [solved?] chromium and glycin

So far, the browser is working fine, but is it safe to believe this? We'll be watching...

tekstryder

Member

Registered: 2013-02-14

Posts: 504

Re: [solved?] chromium and glycin

is it safe to believe this?

Another "fix" was merged:

• https://gitlab.gnome.org/GNOME/glycin/- … quests/302

Why don't you build glycin and test it out?

Or lobby Arch packagers to carry the patch til next tag.

ArchUser2025

Member

Registered: 2025-05-01

Posts: 11

Re: [solved?] chromium and glycin

I believe that Arch packagers are watching the forums and will draw the right conclusions.

tekstryder

Member

Registered: 2013-02-14

Posts: 504

Re: [solved?] chromium and glycin

That commit, and more, have been cherry-picked into glycin 2.0.0-5.

• https://gitlab.archlinux.org/archlinux/ … b2b23b97ee

Typically the packagers pay attention to issues not forum threads.

EDIT: confirmed the many bwrap processes are exiting as expected now.

Last edited by tekstryder (2025-09-26 13:42:09)

ArchUser2025

Member

Registered: 2025-05-01

Posts: 11

Re: [solved?] chromium and glycin

confirmed the many bwrap processes are exiting as expected now.

I confirm that too.
I also confirm that chromium is working with the kernel parameter `kernel.unprivileged_userns_clone = 0 `.
Let's hope that everything is working correctly.