Version-Release number of selected component: virt-manager-4.1.0-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-1378524.scope cmdline: /usr/bin/python3 /usr/bin/virt-manager crash_function: xdrmem_putlong_aligned dso_list: /usr/bin/python3.11 python3-3.11.0-1.fc37.x86_64 (Fedora Project) 1668653208 executable: /usr/bin/python3.11 journald_cursor: s=f3cd73e6bf424f41a93548a20e14e043;i=1234c0;b=ea27dcf41d094116b1f80fc9c69d895d;m=13e20345056;t=5ef2eff47f02e;x=8a8ca4afcee95a10 kernel: 6.0.8-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 xdrmem_putlong_aligned at /usr/src/debug/libtirpc-1.3.3-0.fc37.x86_64/src/xdr_mem.c:136 #1 xdr_u_int at /usr/src/debug/libtirpc-1.3.3-0.fc37.x86_64/src/xdr.c:134 #2 virNetMessageEncodeHeader at ../src/rpc/virnetmessage.c:246 #3 virNetClientProgramCall at ../src/rpc/virnetclientprogram.c:312 #4 callFull at ../src/remote/remote_driver.c:6608 #5 call.isra.0 at ../src/remote/remote_driver.c:6630 #6 remoteConnectGetAllDomainStats at ../src/remote/remote_driver.c:7595 #7 virConnectGetAllDomainStats at ../src/libvirt-domain.c:12549 #8 libvirt_virConnectGetAllDomainStats at /usr/src/debug/libvirt-python-8.6.0-1.fc37.x86_64/libvirt-override.c:9005 #9 cfunction_call at /usr/src/debug/python3.11-3.11.0-1.fc37.x86_64/Objects/methodobject.c:553 Potential duplicate: bug 2093074
Created attachment 1930676 [details] File: backtrace
Created attachment 1930677 [details] File: core_backtrace
Created attachment 1930678 [details] File: cpuinfo
Created attachment 1930679 [details] File: environ
Created attachment 1930680 [details] File: exploitable
Created attachment 1930681 [details] File: limits
Created attachment 1930682 [details] File: maps
Created attachment 1930683 [details] File: mountinfo
Created attachment 1930685 [details] File: open_fds
Created attachment 1930686 [details] File: proc_pid_status
*** Bug 2157624 has been marked as a duplicate of this bug. ***
*** Bug 2158188 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was working in the VM (Windows 10 guest) and while moving the mouse both the VM and the Virt-Manager screens just closed and quit. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-2788720.scope cmdline: /usr/bin/python3 /usr/bin/virt-manager crash_function: xdrmem_putlong_aligned executable: /usr/bin/python3.11 journald_cursor: s=dc009738cb6c4cf89f1242499fc19dcc;i=6d8e731d;b=a45d704b34db4b40878930122dc9b9d1;m=f44ca5ce76;t=5f86d83121ac2;x=31dabb275861a4f0 kernel: 6.2.7-200.fc37.x86_64 package: virt-manager-4.1.0-1.fc37 reason: python3.11 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2185308 has been marked as a duplicate of this bug. ***
Happens approx 1-2 times a week. Virt-manager abruptly exits while running. This tends to happen when virt-manager is in the background/overnight while nothing is interacting with the manager window or VMs. VMs on this system are all vanilla RHEL and Fedora Linux guests, mostly BIOS but a few UEFI guests. There is no obvious pattern to what guests are running when the problem happens. reporter: libreport-2.17.9 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=0c24587da7044c0ea3abeb121c750a11;i=8bba0f;b=168bb9b1ceae45949e3606221b9248f6;m=12b524533a9;t=5f9d7df1aa177;x=cbaca6835a074055 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-4078.slice/user/app.slice/app-gnome-virt\x2dmanager-1442302.scope rootdir: / uid: 4078 kernel: 6.2.9-200.fc37.x86_64 package: virt-manager-4.1.0-1.fc37 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.2-1.fc37.x86_64 (Fedora Project) 1678801044 comment: Happens approx 1-2 times a week. Virt-manager abruptly exits while running. This tends to happen when virt-manager is in the background/overnight while nothing is interacting with the manager window or VMs. VMs on this system are all vanilla RHEL and Fedora Linux guests, mostly BIOS but a few UEFI guests. There is no obvious pattern to what guests are running when the problem happens. backtrace_rating: 4 crash_function: xdrmem_putlong_aligned
*** Bug 2225330 has been marked as a duplicate of this bug. ***
*** Bug 2234332 has been marked as a duplicate of this bug. ***
*** Bug 2238250 has been marked as a duplicate of this bug. ***
*** Bug 2242226 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.