https://bugs.kde.org/show_bug.cgi?id=526540
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- Confirming on Bazzite 44 (Fedora Atomic based), Konsole 26.08.1, toolbox 0.3, podman 5.8.9, Plasma 6.7.5, Frameworks 6.31.0, Qt 6.11.2. Opening Konsole once (by accident, nothing typed) stopped my running rootless containers (PostgreSQL and a long-running batch job). It was the first Konsole start after booting into an image with a newer Podman. From the journal: Konsole started at 21:40:02.958, containers got their stop signals at 21:40:03.14, and ~/.config/toolbox/podman-system-migrate was rewritten and /run/user/1000/toolbox/migrate.lock created at 21:40:03.33. Note that the "remove toolbox" workaround is not available on image-based systems (Bazzite, Kinoite, Silverblue), where toolbox is part of the OS image. The call comes from the eager prefetch in the ContainerRegistry constructor and the background refresh when the container menu is built: https://invent.kde.org/utilities/konsole/-/blob/v26.08.1/src/containers/ContainerRegistry.cpp#L33-L58 https://invent.kde.org/utilities/konsole/-/blob/v26.08.1/src/containers/ToolboxDetector.cpp#L130-L174 https://invent.kde.org/utilities/konsole/-/blob/v26.08.1/src/containers/ContainerList.cpp#L39-L68 Listing Toolbox containers through Podman by label would avoid the side effect, e.g. podman ps -a --filter label=com.github.containers.toolbox=true --format json -- You are receiving this mail because: You are watching all bug changes.
