Version-Release number of selected component: virt-manager-4.1.0-2.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=117b36;b=7ed4dc097cff492d9100db189767cbbf;m=c7aa684f;t=5f638083057ff;x=394648a6fa281aad executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-7286.scope rootdir: / uid: 1000 kernel: 6.2.2-300.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast Truncated backtrace: Thread no. 1 (40 frames) #0 g_type_check_instance_cast at ../gobject/gtype.c:4198 #1 registry_handle_global at ../src/wayland-extensions.c:77 #2 ffi_call_unix64 at ../src/x86/unix64.S:104 #3 ffi_call_int at ../src/x86/ffi64.c:673 #4 ffi_call at ../src/x86/ffi64.c:710 #5 wl_closure_invoke at ../src/connection.c:1025 #6 dispatch_event at ../src/wayland-client.c:1595 #7 dispatch_queue at ../src/wayland-client.c:1741 #8 wl_display_dispatch_queue_pending at ../src/wayland-client.c:1983 #9 wl_display_dispatch_pending at ../src/wayland-client.c:2046 #10 _gdk_wayland_display_queue_events at ../gdk/wayland/gdkeventsource.c:201 #11 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #15 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #16 g_main_context_iteration at ../glib/gmain.c:4343 #17 g_application_run at ../gio/gapplication.c:2573 #18 ffi_call_unix64 at ../src/x86/unix64.S:104 #19 ffi_call_int at ../src/x86/ffi64.c:673 #20 ffi_call at ../src/x86/ffi64.c:710 #21 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684 #22 pygi_function_cache_invoke at ../gi/pygi-cache.c:862 #23 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727 #24 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764 #25 _PyObject_Call at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Objects/call.c:343 #26 _PyEval_EvalFrameDefault at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/ceval.c:5379 #27 _PyEval_EvalFrame at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Include/internal/pycore_ceval.h:73 #28 _PyEval_Vector at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/ceval.c:6435 #29 PyEval_EvalCode at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/ceval.c:1154 #30 run_eval_code_obj at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/pythonrun.c:1714 #31 run_mod at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/pythonrun.c:1735 #32 pyrun_file at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/pythonrun.c:1630 #33 _PyRun_SimpleFileObject at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/pythonrun.c:440 #34 _PyRun_AnyFileObject at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Python/pythonrun.c:79 #35 pymain_run_file_obj at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Modules/main.c:360 #36 pymain_run_file at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Modules/main.c:379 #37 pymain_run_python at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Modules/main.c:601 #38 Py_RunMain at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Modules/main.c:680 #39 Py_BytesMain at /usr/src/debug/python3.11-3.11.2-1.fc38.x86_64/Modules/main.c:734 #40 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 #41 __libc_start_main_impl at ../csu/libc-start.c:360 #42 _start Potential duplicate: bug {crossver_id}
Created attachment 1948278 [details] File: proc_pid_status
Created attachment 1948279 [details] File: maps
Created attachment 1948280 [details] File: limits
Created attachment 1948281 [details] File: environ
Created attachment 1948282 [details] File: open_fds
Created attachment 1948283 [details] File: mountinfo
Created attachment 1948284 [details] File: os_info
Created attachment 1948285 [details] File: cpuinfo
Created attachment 1948286 [details] File: core_backtrace
Created attachment 1948287 [details] File: exploitable
Created attachment 1948288 [details] File: dso_list
Created attachment 1948289 [details] File: backtrace
virt-manager keeps randomly crashing reporter: libreport-2.17.8 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=1bbdb8;b=d42bfa5579c64ababf29d66eaa896eaf;m=1283a2246;t=5f6dbcbc591c4;x=4981a6b99b4a342c executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-12141.scope rootdir: / uid: 1000 kernel: 6.2.6-300.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: virt-manager keeps randomly crashing
Created attachment 1950610 [details] File: backtrace
Another random crash reporter: libreport-2.17.8 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=21d9e5;b=5c083c075d034c0a8a6f312331f58140;m=8db18dce2;t=5f78e2bc21538;x=8b573857878cae18 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-74272.scope rootdir: / uid: 1000 kernel: 6.2.7-300.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.2-1.fc38.x86_64 (Fedora Project) 1678091367 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: Another random crash
Created attachment 1953058 [details] File: backtrace
Running a YouTube video in Microsoft Edge inside a Windows 11 VM running in virt-manager. Always crashes the virt-manager application. The VMs continue running. As soon as I reconnect to the VM running Windows (where youtube video is still playing) it virt-manager crashes again reporter: libreport-2.17.9 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=2825e41c1f3f43688dd5401d2f212bb8;i=33d94;b=f4815ac3e5884cfbb57dae1229f47755;m=1f88e67d3;t=5f8241ab3521e;x=b55b7a9cb804222a executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1002.slice/user/app.slice/app-gnome-virt\x2dmanager-33317.scope rootdir: / uid: 1002 kernel: 6.2.8-300.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: Running a YouTube video in Microsoft Edge inside a Windows 11 VM running in virt-manager. Always crashes the virt-manager application. The VMs continue running. As soon as I reconnect to the VM running Windows (where youtube video is still playing) it virt-manager crashes again
Problem appears to occur during login or when first returning to the system after an extended period of the system being idle. Judging from the timestamp on the report, virt-manager didn't crash until I began to use the system after leaving it on overnight. Power mode is set to balanced. Automatic suspend is turned off. I installed the COPR 6.1 LTS kernel since I didn't have ZFS support on 6.2 or 6.3, but otherwise this is a stock system with little else but virt-manager and ZFS installed. reporter: libreport-2.17.10 journald_cursor: s=448998e0f672443180af0e5906caefb3;i=857e;b=208e0361a8b847db92119967c3ded1c3;m=bfe30d51d;t=5fd500a61e8cf;x=64ab2fd83861e9fb executable: /usr/bin/python3.11 reason: python3.11 killed by SIGSEGV backtrace_rating: 4 package: virt-manager-4.1.0-2.fc38 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-7178.scope rootdir: / crash_function: g_type_check_instance_cast dso_list: /usr/bin/python3.11 python3-3.11.3-2.fc38.x86_64 (Fedora Project) 1685834734 type: CCpp runlevel: N 5 cmdline: /usr/bin/python3 /usr/bin/virt-manager kernel: 6.1.30-200.fc38.x86_64 uid: 1000
I don't really know what caused this problem. I tried an update on a Fedora VM and something bad happened, lost all icons for everything everywhere. I shutdown and used the snapshot system to roll back, try again. It was taking a while so I left it alone. When I logged in next, I got this crash that said it happend "now", but I wonder if it really happened eariler during the rollback. reporter: libreport-2.17.10 cgroup: 0::/user.slice/user-13013.slice/user/app.slice/app-gnome-virt\x2dmanager-1874775.scope journald_cursor: s=abf84a23ee494b84803b5b10fd803add;i=300806;b=153914c111c84515877c28d90918a928;m=23cfb5897c;t=5ff0c410fe039;x=837b0516b2295110 cmdline: /usr/bin/python3 /usr/bin/virt-manager package: virt-manager-4.1.0-2.fc38 crash_function: g_type_check_instance_cast type: CCpp backtrace_rating: 4 executable: /usr/bin/python3.11 reason: python3.11 killed by SIGSEGV rootdir: / runlevel: N 5 kernel: 6.3.8-200.fc38.x86_64
Okay, it happened again, and no VMs were running, just the manager. Happened right when I logged in to the lock screen.
I was upgrading a Debian virtual machine from 11 to 12 reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=83f395a2bbd34ad49738150c33df2a6b;i=35bb6a;b=2ccb8999941d4331a95b56bdc9d5569d;m=621ec87cb;t=60064a82a0b6c;x=3d649d88ec934dd executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-24774.scope rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.4-1.fc38.x86_64 (Fedora Project) 1688130522 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: I was upgrading a Debian virtual machine from 11 to 12
- running Kali Linux VM in virt-manager - disconnect and reconnect USB-C docking station (ethernet, two monitors, power, and mouse) Host: Fedora 38 Kernel: 6.3.12-200 Virt-Manager version: 4.1.0 reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=da09cf45f434434ba216f9c3e5a7505b;i=3f6b42;b=d6d3e975b95a48ea93998a37aed1249c;m=226c21794c;t=600d5755c0573;x=b76d0f0bb783c259 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-119427.scope rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.4-1.fc38.x86_64 (Fedora Project) 1688217846 backtrace_rating: 4 crash_function: g_type_check_instance_cast
Tried to open up Firefox on native O/S when running a VM (Win11) reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=2e1b8056ba74414498319d010ccd46ea;i=e68a1;b=561ae4e931e9499c98d7b91dddea56da;m=535a9a236;t=601005cde27f3;x=df455783db828483 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-8170.scope rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: Tried to open up Firefox on native O/S when running a VM (Win11)
* Ran some VMs (connected with SPICE channel I belive) * Closed connections (leaving VMs running) and locked computer for lunch * Found crash report when returning (and unlocking computer) In case it happens to be related, KDE's plasmashell seems to be having an error, as the bar is not updating or drawn correctly. reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=7ca2c48dff4146568f81a85246aaf3a4;i=35b9063;b=23efc8b19c4f40cbb9c3b270bde02047;m=221fc638f6;t=60371ec763de3;x=f30b2413fc2dcc6b executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-virt\x2dmanager-d585b915f1424215abf7c385abface7a.scope rootdir: / uid: 1000 kernel: 6.4.11-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.4-1.fc38.x86_64 (Fedora Project) 1686831415 backtrace_rating: 4 crash_function: g_type_check_instance_cast
Created a Windows 10 VM, turned off the VM and took a snapshot. Left Virt-Manager open and walk away for around 10 min, after come back the application was closed and ABRT reported the problem reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=91a1c82dfca9493683e7d12450db6c5c;i=6b68;b=ef9fd8ed1429446a97d80f1441449082;m=12553fb51;t=60384257ce529;x=9860956a775a63e0 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-6098.scope rootdir: / uid: 1000 kernel: 6.4.11-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast
slapped the lid shut on the laptop and shoved computer in bag reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=8c8b2c0d57b24c1c9fb9f4421045734c;i=648712;b=d79c8bc171f1463b87c212feca279851;m=1c133e21b8;t=604824ba9bbe2;x=d6262da943f1c7a4 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-14707.scope rootdir: / uid: 1000 kernel: 6.4.11-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.4-1.fc38.x86_64 (Fedora Project) 1688392031 comment: slapped the lid shut on the laptop and shoved computer in bag backtrace_rating: 4 crash_function: g_type_check_instance_cast
Intellij IDEA was performing static code analysis on a project within a Debian VM when this occurred. reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=6110ae456ee84182a371d3775502374f;i=77cb9a;b=4c4dcb2306e5429bae0e9d064dff05fa;m=2b01ec112;t=607ecf8a13441;x=c6be705c91bfd3a3 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-4583.scope rootdir: / uid: 1000 kernel: 6.5.6-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.6-1.fc38.x86_64 (Fedora Project) 1697475459 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: Intellij IDEA was performing static code analysis on a project within a Debian VM when this occurred.
Connected to dock (means resources added) and happened after wake up. reporter: libreport-2.17.11 type: CCpp reason: python3.11 killed by SIGSEGV journald_cursor: s=a912bf5a4872485cace5833490802f3a;i=4ab8c66;b=066f222e2145460e8e988f972c4acc82;m=1c46b08423;t=609a18157574d;x=1d6e0a8b75402b86 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/bin/virt-manager cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-virt\x2dmanager-254306.scope rootdir: / uid: 1000 kernel: 6.5.9-200.fc38.x86_64 package: virt-manager-4.1.0-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_cast comment: Connected to dock (means resources added) and happened after wake up.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 '38'. 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 38 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 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.