Version-Release number of selected component: virt-manager-4.0.0-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-13013.slice/user/app.slice/myvms.service cmdline: /usr/bin/python3 /usr/bin/virt-manager crash_function: xdrmem_putlong_aligned dso_list: /usr/bin/python3.10 python3-3.10.4-1.fc36.x86_64 (Fedora Project) 1652656916 executable: /usr/bin/python3.10 journald_cursor: s=07f9fc9a596847b094ec9077e691ae2d;i=d70f71;b=9c6ec8266a684b4e806b63224a4fb685;m=5e7972b0e2;t=5e077fc2fb7bd;x=389e0a57f4c2f66c kernel: 5.17.9-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 13013 Truncated backtrace: Thread no. 1 (10 frames) #0 xdrmem_putlong_aligned at /usr/src/debug/libtirpc-1.3.2-1.rc1.fc36.1.x86_64/src/xdr_mem.c:136 #1 xdr_u_int at /usr/src/debug/libtirpc-1.3.2-1.rc1.fc36.1.x86_64/src/xdr.c:134 #2 virNetMessageEncodeHeader at ../src/rpc/virnetmessage.c:240 #3 virNetClientProgramCall at ../src/rpc/virnetclientprogram.c:312 #4 callFull at ../src/remote/remote_driver.c:6554 #5 call.isra.0 at ../src/remote/remote_driver.c:6576 #6 remoteNodeGetInfo at src/remote/remote_client_bodies.h:7439 #7 virNodeGetInfo at ../src/libvirt-host.c:432 #8 libvirt_virNodeGetInfo at /usr/src/debug/libvirt-python-8.0.0-2.fc36.x86_64/libvirt-override.c:2833 #9 cfunction_call at /usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Objects/methodobject.c:552
Created attachment 1886166 [details] File: backtrace
Created attachment 1886167 [details] File: core_backtrace
Created attachment 1886168 [details] File: cpuinfo
Created attachment 1886169 [details] File: environ
Created attachment 1886170 [details] File: exploitable
Created attachment 1886171 [details] File: limits
Created attachment 1886172 [details] File: maps
Created attachment 1886173 [details] File: mountinfo
Created attachment 1886174 [details] File: open_fds
Created attachment 1886175 [details] File: proc_pid_status
Similar problem has been detected: As far as I know, NOTHING caused this problem. I start virtmanager when I login because I regularly use my VMs for different things. But, sometimes, like this time, virtmanager just crashes after it's been running for a while; I didn't even start any VMs since the last time I reboot the host. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-13013.slice/user/app.slice/myvms.service cmdline: /usr/bin/python3 /usr/bin/virt-manager crash_function: xdrmem_putlong_aligned dso_list: /usr/bin/python3.10 python3-3.10.4-1.fc36.x86_64 (Fedora Project) 1652656916 executable: /usr/bin/python3.10 journald_cursor: s=07f9fc9a596847b094ec9077e691ae2d;i=d8d53f;b=525a1d5e9cdc40e6b594f2892c56e30e;m=5ec14509d8;t=5e1435e3ecb1a;x=b86c46eff42d2975 kernel: 5.17.12-300.fc36.x86_64 package: virt-manager-4.0.0-1.fc36 reason: python3.10 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 13013
Same thing happened to me. I thought abrt was going to report it here, but it looks like that didn't happen. It at least gave me this link anyway.
Same thing, left virtmanager open (in the tray) overnight, and had this crash reported as happening ~1am when I came back this morning.
*** Bug 2154547 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.