Version-Release number of selected component: 2:podman-1.9.1-1.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: containers-rootlessport crash_function: runtime.raise executable: /usr/bin/podman journald_cursor: s=5936d5a7b0834cf899b2d0e142eb3d75;i=1f9629;b=fe2c2ebe88cb4f679db342610c2616d8;m=7b5d42a6d;t=5a4d2ad51058e;x=11fe6e569e31f5c4 kernel: 5.6.8-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 runtime.raise at /usr/lib/golang/src/runtime/sys_linux_amd64.s:165 #1 runtime.dieFromSignal at /usr/lib/golang/src/runtime/signal_unix.go:729 #2 runtime.sigfwdgo at /usr/lib/golang/src/runtime/signal_unix.go:943 #3 runtime.sigtrampgo at /usr/lib/golang/src/runtime/signal_unix.go:412 #4 runtime.sigtramp at /usr/lib/golang/src/runtime/sys_linux_amd64.s:389 #6 runtime.raise at /usr/lib/golang/src/runtime/sys_linux_amd64.s:165 #7 runtime.dieFromSignal at /usr/lib/golang/src/runtime/signal_unix.go:729 #8 runtime.crash at /usr/lib/golang/src/runtime/signal_unix.go:821 #9 runtime.fatalpanic at /usr/lib/golang/src/runtime/panic.go:1216 #10 runtime.gopanic at /usr/lib/golang/src/runtime/panic.go:1064
Created attachment 1684823 [details] File: backtrace
Created attachment 1684824 [details] File: cgroup
Created attachment 1684825 [details] File: core_backtrace
Created attachment 1684826 [details] File: cpuinfo
Created attachment 1684827 [details] File: dso_list
Created attachment 1684828 [details] File: environ
Created attachment 1684829 [details] File: limits
Created attachment 1684830 [details] File: maps
Created attachment 1684831 [details] File: mountinfo
Created attachment 1684832 [details] File: open_fds
Created attachment 1684834 [details] File: proc_pid_status
Similar problem has been detected: Happens after stopping a container in podman reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: containers-rootlessport crash_function: runtime.raise executable: /usr/bin/podman journald_cursor: s=5936d5a7b0834cf899b2d0e142eb3d75;i=202d52;b=fe2c2ebe88cb4f679db342610c2616d8;m=e3a0d6104;t=5a4e4274201b3;x=142ca83813c598f5 kernel: 5.6.8-300.fc32.x86_64 package: 2:podman-1.9.1-1.fc32 reason: podman killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Think we've chased this one down upstream - https://github.com/containers/libpod/issues/6018 It's already fixed in master, and we're planning a release early next week which will include the fix.
*** Bug 1832142 has been marked as a duplicate of this bug. ***
*** Bug 1834237 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Have used a container yesterday, today i was greeted with this error on cold boot. reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ac331b0a-6f35-4e09-817f-df69f028bdc5.scope cmdline: containers-rootlessport crash_function: runtime.raise executable: /usr/bin/podman journald_cursor: s=9fde0a668e664dd6a2a5eb3f9c95220c;i=1ce7cc;b=43d94e6679dc4ad3a69273594995cb1b;m=77fd73a7f;t=5a561b01fe633;x=810260e16635e829 kernel: 5.6.8-300.fc32.x86_64 package: 2:podman-1.9.1-1.fc32 reason: podman killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1834713 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Hi That's what I've done - turn on computer - wait for Fedora Login screen, then I left my computer for 10 minutes (so I didn't login) - screen switched off due to inactivity - when I back I've seen a Problem Reporting icon on the login screen Well, yesterday I've upgraded some packages ➜ ~ dnf history info 25 Return-Code : Success Releasever : 32 Command Line : update Packages Altered: Install kernel-5.6.11-300.fc32.x86_64 @updates Install kernel-core-5.6.11-300.fc32.x86_64 @updates Install kernel-devel-5.6.11-300.fc32.x86_64 @updates Install kernel-modules-5.6.11-300.fc32.x86_64 @updates Install kernel-modules-extra-5.6.11-300.fc32.x86_64 @updates Upgrade gnome-clocks-3.36.2-1.fc32.x86_64 @updates Upgraded gnome-clocks-3.36.0-2.fc32.x86_64 @@System Upgrade kernel-headers-5.6.11-300.fc32.x86_64 @updates Upgraded kernel-headers-5.6.10-300.fc32.x86_64 @@System Upgrade oniguruma-6.9.5-1.rev1.fc32.x86_64 @updates Upgraded oniguruma-6.9.4-1.fc32.1.x86_64 @@System Upgrade python3-gobject-3.36.1-1.fc32.x86_64 @updates Upgraded python3-gobject-3.36.0-2.fc32.x86_64 @@System Upgrade python3-gobject-base-3.36.1-1.fc32.x86_64 @updates Upgraded python3-gobject-base-3.36.0-2.fc32.x86_64 @@System Upgrade webkit2gtk3-2.28.2-2.fc32.x86_64 @updates Upgraded webkit2gtk3-2.28.2-1.fc32.x86_64 @@System Upgrade webkit2gtk3-jsc-2.28.2-2.fc32.x86_64 @updates Upgraded webkit2gtk3-jsc-2.28.2-1.fc32.x86_64 @@System Removed kernel-5.6.7-300.fc32.x86_64 @@System Removed kernel-core-5.6.7-300.fc32.x86_64 @@System Removed kernel-devel-5.6.7-300.fc32.x86_64 @@System Removed kernel-modules-5.6.7-300.fc32.x86_64 @@System Removed kernel-modules-extra-5.6.7-300.fc32.x86_64 @@System reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-081fb012-3a94-4cba-84ac-5a2808e63f2e.scope cmdline: containers-rootlessport crash_function: runtime.raise executable: /usr/bin/podman journald_cursor: s=bba0e3af49dc4fb389af781f94ee9f25;i=20e76;b=a10a85b94d1e449fafd939996cfdfb9c;m=c71567591;t=5a57384c4835a;x=ec5040e9931d4690 kernel: 5.6.10-300.fc32.x86_64 package: 2:podman-1.9.1-1.fc32 reason: podman killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Closing, please reopen if issue isn't fixed.