Description of problem: Cannot reproduce, virt-manager crashed with view of VM being minimized and VM with 3D accel (virtio3d + OpenGL) was running. Crashed after deminimizing it. virt-manager-1.6.0-1.3.git3bc7ff24c.fc29.noarch Version-Release number of selected component: virt-manager-1.6.0-1.3.git3bc7ff24c.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/python3 /usr/share/virt-manager/virt-manager crash_function: poll_for_event executable: /usr/bin/python3.7 journald_cursor: s=4ca6e09ab8d944ba98161b85003cd8a0;i=12c11;b=2f73074b85a84ae0be56957b4d9eb3eb;m=132669173e;t=576c5f4d124e3;x=87823582cf5b1fc4 kernel: 4.18.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1598901
Created attachment 1487228 [details] File: backtrace
Created attachment 1487229 [details] File: cgroup
Created attachment 1487230 [details] File: core_backtrace
Created attachment 1487231 [details] File: cpuinfo
Created attachment 1487232 [details] File: dso_list
Created attachment 1487233 [details] File: environ
Created attachment 1487234 [details] File: limits
Created attachment 1487235 [details] File: maps
Created attachment 1487236 [details] File: mountinfo
Created attachment 1487237 [details] File: open_fds
Created attachment 1487238 [details] File: proc_pid_status
Similar problem has been detected: After typing my root password and/or my User creation reporter: libreport-2.9.6 backtrace_rating: 3 cmdline: /usr/bin/python3 /usr/share/virt-manager/virt-manager crash_function: poll_for_event executable: /usr/bin/python3.7 journald_cursor: s=d8cb9e0594bd4255beac5160eda528c7;i=79a12;b=be343f27f0a140fb97dc23ff3db908ee;m=8322c482;t=578d5d3e5f11e;x=1a1fd8528f769131 kernel: 4.18.15-300.fc29.x86_64 package: virt-manager-2.0.0-1.fc29 reason: python3.7 killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I connected to a couple hypervisors via SSH, started ~3 VMs and started OS installation in them from PXE. Then when I was clicking the installation workflow in one of the VMs virt manager crashed and all of its windows vanished. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/virt-manager/virt-manager crash_function: poll_for_event executable: /usr/bin/python3.7 journald_cursor: s=7ff0aed861404bcc92ed4c3b225489ca;i=2ce0;b=934f628ef61a4e8b91b83917f273a44f;m=af90c3ef;t=57cac92b3d1d4;x=f560172ea416c117 kernel: 4.19.6-300.fc29.x86_64 package: virt-manager-1.6.0-1.3.git3bc7ff24c.fc29 reason: python3.7 killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1513106 [details] File: backtrace
*** Bug 1677326 has been marked as a duplicate of this bug. ***
*** Bug 1657338 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just runned virtual machine for some minutes. After restart virt-manager all working as a charm. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/virt-manager/virt-manager crash_function: poll_for_event executable: /usr/bin/python3.7 journald_cursor: s=5dca42b84e4c4dae89a7c8ccc89284e8;i=44cb;b=4eed7c951d6f4933967970ebcd47adce;m=79b3ec634;t=5861ea60a6aeb;x=dffe6f87966ac17c kernel: 5.0.5-200.fc29.x86_64 package: virt-manager-2.1.0-1.fc29 reason: python3.7 killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Hapened during switching desktops in Gnome 3. I hit Ctrl+Alt to release mouse, and then Ctrl+Alt+UpArrow to go to upper desktop. I was remotely vewing spice display of win10 VM running on KVM. Both kvm host and viewer are running the same, latest (as per of Apr 30th) updates of Fedora 29. reporter: libreport-2.10.0 backtrace_rating: 3 cmdline: /usr/bin/python3 /usr/share/virt-manager/virt-manager crash_function: poll_for_event executable: /usr/bin/python3.7 journald_cursor: s=1ebc32375adf4b0293fba956aa47920b;i=177951;b=be5e6969cb494d738356fc429dd5e439;m=12382ae7d;t=587c0aa384507;x=b336d6a4a661fac6 kernel: 5.0.9-200.fc29.x86_64 package: virt-manager-2.1.0-2.fc29 reason: python3.7 killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1711254 has been marked as a duplicate of this bug. ***
*** Bug 1707031 has been marked as a duplicate of this bug. ***
*** Bug 1683608 has been marked as a duplicate of this bug. ***
*** Bug 1597341 has been marked as a duplicate of this bug. ***
*** Bug 1720955 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
2018-09-26 13:16:39 UTC - date/time of report 2019-04-30 15:10:57 UTC - last report of this bug 2019-11-27 22:54:17 UTC - date time of closure as won't fix Seriously - WHY DIDNT YOU FIX THAT!!! You had one year for fixing this issue yet you just tell the users to f*ck off. What is even the point for users to use your OS anymore if you are UNVILLING to fix the bugs during its lifetime. Your last comment AFTER MORE THAN A YEAR OF THE INITIAL REPORT is that if we can reproduce it than we should report it, Why? Beased on your behaviour you would still tell the users to f*ck of. And yes I have encountered this issue over the last yeer on weekly basis. But during that time my OS was supported just fine so I periodically checked for updates. Now I am absolutely disgusted by your support. Edit: And yes, I know that this is public comment but the community should know how are you treating them. This is not the first bug that you did not care and is definitelly not the last. Well for me it is the last because I am switching to UNIX.
I shouldn't have let this auto close (which is done by a script when the targeted Fedora version goes End of Life). That was my mistake. The same issue is tracked in multiple other reports elsewhere against virt-manager in bugzilla.redhat.com so it isn't forgotten, or an acknowledgement that there's no plans to fix; I do plan to fit it. Unfortunately the issue is some kind of threading related crash which is hard to pinpoint unless I can consistently reproduce, which I can't. My plan has been to audit all the threading code when I get time, but I haven't found the time yet.