Bwrap and glycin processes, how comes?

[hape]

Since last stable update (i suppose as i didn’t notice this before), i occasionally find several bwrap and glycin processes. They seem to do now harm, but does anyone know what these do and what causes them to appear? First time i found them i ran digikam (nativ install from Manjaro repos), but these processes seem to appear also without digikam.

I don’t have any snap or flatpaks running (to my knowledge).

sample ps -ax:

> 120644 ?        I      0:00 \[kworker/2:0-i915-unordered\]
> 120746 ?        S      0:00 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/stor
> 120748 ?        S      0:00 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/stor
> 120749 ?        Sl     0:00 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 20
> 120763 ?        S      0:00 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/stor
> 120769 ?        S      0:00 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/stor
> 120770 ?        S      0:00 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/stor
> 120772 ?        S      0:00 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/stor
> 120773 ?        Sl     0:00 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 50
> 120774 ?        S      0:00 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/stor
> 120778 ?        S      0:00 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/stor
> 120780 ?        Sl     0:00 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 28
> 120781 ?        Sl     0:00 /usr/lib/glycin-loaders/2+/glycin-image-rs --dbus-fd 21
> 120809 pts/0    R+     0:00 ps ax

HP

[linux-aarhus]

An is sandboxed using bubblewrap

Searching for bwrap reveals (among other things) it is owned by the bubblewrap package which is a sandboxing tool

 $ pamac search -f bwrap
...
/usr/bin/bwrap is owned by bubblewrap
...

 $ pacman -Qi bubblewrap
Name            : bubblewrap
Version         : 0.11.0-1
Description     : Unprivileged sandboxing tool
Architecture    : x86_64
URL             : https://github.com/containers/bubblewrap
Licenses        : LGPL-2.0-or-later
Groups          : None
Provides        : None
Depends On      : gcc-libs  glibc  libcap
Optional Deps   : None
Required By     : flatpak  glycin  webkit2gtk-4.1
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 97,03 KiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : ons 30 okt 2024 22:18:35 CET
Install Date    : man 22 sep 2025 06:46:27 CEST
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

[hape]

to reply myself: seems that gdk-pixbuf pulls in this stuff, it depends on clycin, which depends on bubblewrap. Linux dependency-hell