Stéphane Travostino

> What I'd suggest here is to use a non-root user for the container, which will bypass the `chown` behavior entirely (`docker run --user 1000 ...`). Not really, the `tar`...

@thunderburger what do you mean that you are having the same issue with 1.5.0.2? I rebased my Silverblue workstation to 39.20231120.0, which is on 1.5.0.2, and the problem disappears. I'll...

@89luca89 Any update? I am still on the distrobox 1.5 until this gets resolved. I really do not want to rebuild my archlinux container I've used for 2 years. I...

See also: https://github.com/containers/podman/discussions/19944

toolbox has been having the same issue, linking all related discussions here for cross-reference: https://github.com/containers/toolbox/pull/1207 https://github.com/containers/toolbox/issues/1204

After some back and forth, it does seem to be a distrobox bug. Basically, podman forwards SIGHUPs it receives. But the problem is `distrobox-enter` basically runs a `podman exec -i...

+1 here. Consider either bind-mounting the host's fonts, or making each fontconfig completely independent. Case in point: my host is Fedora Silverblue, my distrobox is Arch Linux, which has GNOME...

See also https://github.com/elixir-tools/next-ls/issues/359

> installing `dbus-x11` and using `dbus-launch flatpak update --noninteractive` worked for me on Fedora 36 Silverblue. Keep in mind that recent Fedora versions have adopted dbus-broker, so `/usr/bin/dbus-launch` doesn't exist...

Sure, though I don't know how to get started with that. Do you have any pointers?