Bug 1036709

Summary: [abrt] virt-manager-0.10.0-4.fc19: _g_log_abort: Process /usr/bin/python2.7 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: pygobject3Assignee: John (J5) Palmieri <john.j5live>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: berrange, crobinso, icq, john.j5live, virt-maint, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/90e3553aba7a7ac6f96c8519e6aa2bf01593d7e6
Whiteboard: abrt_hash:90222cf06c413eba937e81e1232bcb99d55361f8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-11 22:14:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description David Juran 2013-12-02 13:58:40 UTC 
Version-Release number of selected component:
virt-manager-0.10.0-4.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/share/virt-manager/virt-manager
crash_function: _g_log_abort
executable:     /usr/bin/python2.7
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            500
var_log_messages: Dec  2 13:51:49 localhost abrt-hook-ccpp[27115]: Saved core dump of pid 25841 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-12-02-13:51:42-25841 (175972352 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:255
 #4 g_callable_info_is_method at girepository/gicallableinfo.c:150
 #5 g_callable_info_get_ffi_arg_types at girepository/girffi.c:167
 #6 g_callable_info_prepare_closure at girepository/girffi.c:373
 #7 _pygi_make_native_closure at pygi-closure.c:637
 #8 _pygi_marshal_from_py_interface_callback at pygi-marshal-from-py.c:1473
 #9 _invoke_marshal_in_args at pygi-invoke.c:515
 #10 pygi_callable_info_invoke at pygi-invoke.c:659
 #11 ext_do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4408
 #12 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2779
Comment 1 David Juran 2013-12-02 13:58:53 UTC 
Created attachment 831579 [details]
File: backtrace
Comment 2 David Juran 2013-12-02 13:58:58 UTC 
Created attachment 831580 [details]
File: cgroup
Comment 3 David Juran 2013-12-02 13:59:04 UTC 
Created attachment 831581 [details]
File: core_backtrace
Comment 4 David Juran 2013-12-02 13:59:11 UTC 
Created attachment 831582 [details]
File: dso_list
Comment 5 David Juran 2013-12-02 13:59:16 UTC 
Created attachment 831583 [details]
File: environ
Comment 6 David Juran 2013-12-02 13:59:21 UTC 
Created attachment 831584 [details]
File: limits
Comment 7 David Juran 2013-12-02 13:59:27 UTC 
Created attachment 831585 [details]
File: maps
Comment 8 David Juran 2013-12-02 13:59:31 UTC 
Created attachment 831586 [details]
File: open_fds
Comment 9 David Juran 2013-12-02 13:59:36 UTC 
Created attachment 831587 [details]
File: proc_pid_status
Comment 10 David Juran 2013-12-02 14:18:35 UTC 
Do note that I'm running glib2-2.38.2-1 from F20 on F19
Comment 11 Cole Robinson 2013-12-02 19:29:49 UTC 
(In reply to David Juran from comment #10)
> Do note that I'm running glib2-2.38.2-1 from F20 on F19

Why? Maybe try pulling in f20 pygobject3 as well, could be something that's already fixed there.

How reproducible is this?
Comment 12 David Juran 2013-12-05 15:20:01 UTC 
Why I'm running glib2 from F20? I needed to update evolution (long story) and it required newer glib2 due to silent ABI change, there are was some symbol in F20 glib2 that wasn't in F19.

Regarding reproducibility, this crash has only happened one single time so feel free to close the bug, hopefully it's caused by the non-standard package-mix.
Comment 13 Colin Walters 2013-12-05 15:22:19 UTC 
(In reply to David Juran from comment #12)
> it required newer glib2 due to silent ABI change, there are was some
> symbol in F20 glib2 that wasn't in F19.

Er...it's totally expected that newer GLib versions have more symbols, but if you're claiming there was a *break*, please provide more information.
Comment 14 Cole Robinson 2014-01-11 22:14:00 UTC 

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