Bug 1756065

Summary: [abrt] virt-manager: poll_for_event(): python3.7 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Tomas Toth <ttomasz>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: anatoliy.osipov, andy, berrange, crobinso, elxreno, error, fziglio, ibm.plg, kalus.mario, pdimitrov, philip.wyett, zemeterisan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ed0983700ded4c9acdd2f185748a7f5ca2914b7a
Whiteboard: abrt_hash:c58ecf5c70ff1e505f57bba3f799768e4ea2ed9d;VARIANT_ID=kde;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-29 17:37:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
Screenshot from available updates none

Description Tomas Toth 2019-09-26 17:01:59 UTC
Description of problem:
Restarted VM (from inside guest).

Version-Release number of selected component:
virt-manager-2.2.1-2.fc31

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/bin/python3 /usr/share/virt-manager/virt-manager
crash_function: poll_for_event
executable:     /usr/bin/python3.7
journald_cursor: s=85950af18a944b6ab78d8f1a5a9e7d61;i=37ede;b=a2f5c33e4ae146e29b7605d5c6456fe2;m=7d15f6d2a;t=59377655e7964;x=5848042d85fc6a3a
kernel:         5.3.0-1.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 0 (10 frames)
 #4 poll_for_event at xcb_io.c:260
 #5 poll_for_response at xcb_io.c:278
 #8 XPending at Pending.c:55
 #9 gdk_check_xpending at gdkeventsource.c:269
 #10 gdk_event_source_prepare at gdkeventsource.c:287
 #11 g_main_context_prepare at ../glib/gmain.c:3489
 #13 g_main_context_iteration at ../glib/gmain.c:3978
 #14 g_application_run at ../gio/gapplication.c:2559
 #15 ffi_call_unix64 at ../src/x86/unix64.S:76
 #16 ffi_call at ../src/x86/ffi64.c:525

Potential duplicate: bug 1633231

Comment 1 Tomas Toth 2019-09-26 17:02:04 UTC
Created attachment 1619650 [details]
File: backtrace

Comment 2 Tomas Toth 2019-09-26 17:02:06 UTC
Created attachment 1619651 [details]
File: core_backtrace

Comment 3 Tomas Toth 2019-09-26 17:02:07 UTC
Created attachment 1619652 [details]
File: cpuinfo

Comment 4 Tomas Toth 2019-09-26 17:02:09 UTC
Created attachment 1619653 [details]
File: dso_list

Comment 5 Tomas Toth 2019-09-26 17:02:11 UTC
Created attachment 1619654 [details]
File: environ

Comment 6 Tomas Toth 2019-09-26 17:02:12 UTC
Created attachment 1619655 [details]
File: limits

Comment 7 Tomas Toth 2019-09-26 17:02:14 UTC
Created attachment 1619656 [details]
File: maps

Comment 8 Tomas Toth 2019-09-26 17:02:16 UTC
Created attachment 1619657 [details]
File: mountinfo

Comment 9 Tomas Toth 2019-09-26 17:02:17 UTC
Created attachment 1619658 [details]
File: open_fds

Comment 10 Tomas Toth 2019-09-26 17:02:19 UTC
Created attachment 1619659 [details]
File: proc_pid_status

Comment 11 kalus.mario 2020-01-15 12:23:34 UTC
Similar problem has been detected:

Working vith QEMU Virt Manager - doing some stuff inside virtual machines (testing some products).
All virtual OS had been disconnected and QEMU Virt Manager shutdown unexpectedly

reporter:       libreport-2.11.3
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        /usr/bin/python3 /usr/share/virt-manager/virt-manager
crash_function: poll_for_event
executable:     /usr/bin/python3.7
journald_cursor: s=92a4313359c6417bbf50c2b1be7f4486;i=44b4;b=50f1d6fa92454328b2fab9be4c34388e;m=35a33e0785;t=59c2c8cfc0851;x=3da36ce1e6dbeda7
kernel:         5.4.8-200.fc31.x86_64
package:        virt-manager-2.2.1-2.fc31
reason:         python3.7 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 12 kalus.mario 2020-01-15 12:39:04 UTC
THis issue WAS REPORTED in https://bugzilla.redhat.com/show_bug.cgi?id=1633231
You have done nothing over the year and than closed the bug due to "OS is no longer supported"

Let me remind you - it was reproduced on Fedora 29, 30 and now 31. Do you think that it is appropriate to not even look at it because based on the Fedora 31 milestones its EOL is planned on Wednesdaz 2020/12-02.

By the way - none of the available updates for the affected systems is related to virt-manager nor Python 3.7. Therefore Telling me to try to update the system is usesless.

Comment 13 Cole Robinson 2020-01-15 20:21:36 UTC
*** Bug 1714017 has been marked as a duplicate of this bug. ***

Comment 14 Cole Robinson 2020-01-15 20:21:38 UTC
*** Bug 1749072 has been marked as a duplicate of this bug. ***

Comment 15 Cole Robinson 2020-01-15 20:22:57 UTC
*** Bug 1749740 has been marked as a duplicate of this bug. ***

Comment 16 Cole Robinson 2020-01-15 20:23:23 UTC
*** Bug 1758748 has been marked as a duplicate of this bug. ***

Comment 17 Cole Robinson 2020-01-15 20:23:58 UTC
*** Bug 1783162 has been marked as a duplicate of this bug. ***

Comment 18 Cole Robinson 2020-01-15 20:42:13 UTC
Sorry, I haven't been able to reproduce so it's tough to fix. The bugs getting closed is from Fedoras end-of-life script, it's not really a human doing it.

For those that can reliably reproduce, a few things that will help:

* Are any of your VMs using spice GL?
* This reproduces on fully up to date fedora31?
* Is there any reliable steps to reproduce?
* Is python3-libguestfs installed? Is 'libguest VM introspection' enabled in Edit->Preferences ?
* Are you using the system tray icon?

Also if anyone can reliably reproduce, please attach ~/.cache/virt-manager/virt-manager.log from after you hit the crash, and make a note of the time when the app crashes

Comment 19 Michael Hampton 2020-01-15 21:23:35 UTC
For my part I haven't seen this occur since last September. I would guess that since the crash appeared to be in some GTK+ code that some update to GTK may have fixed it.

Comment 20 kalus.mario 2020-01-15 22:44:56 UTC
To be clear (response to the GTK+ code) - my system is almost up2date. I have attached screenshot from dnf --refresh update There is no virt-manager, Python or GTK related package to be updated. Fedora 29 was up2date as well (I have ran dnf --refresh update on that OS as well prior upgrading it to newer Fedora).

Comment 21 kalus.mario 2020-01-15 22:48:07 UTC
Created attachment 1652582 [details]
Screenshot from available updates

Comment 22 pleg 2020-01-23 14:58:53 UTC
*** Bug 1794425 has been marked as a duplicate of this bug. ***

Comment 23 Cole Robinson 2020-01-23 17:01:49 UTC
Does this always crash for people when they are interacting with a VM graphical console?

FWIW there's a bug from a debian user who can reproduce regularly. I'm trying to debug this with them too. I'm starting to think this may be spice-gtk issue too so I've asked for help on spice-devel

https://bugzilla.redhat.com/show_bug.cgi?id=1792576

Comment 24 Frediano Ziglio 2020-01-29 17:37:59 UTC

*** This bug has been marked as a duplicate of bug 1758384 ***