Bug 1267575

Summary: [abrt] gnome-boxes: boxes_machine_real_disconnect_display(): gnome-boxes killed by SIGSEGV
Product: [Fedora] Fedora Reporter: chanueting <chanueting>
Component: gnome-boxesAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: cfergeau, chanueting, fidencio, gnome-sig, marcandre.lureau, virt-maint, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4b5f23d8098f3f5c1672c916588e36ae510d1c1e
Whiteboard: abrt_hash:9a0fbb45081743a8c330a4a1542b62d270d76112;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:03:57 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description chanueting 2015-09-30 12:39:19 UTC 
Description of problem:
Close the gnome-boxes window.

Version-Release number of selected component:
gnome-boxes-3.16.2-4.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        gnome-boxes
crash_function: boxes_machine_real_disconnect_display
executable:     /usr/bin/gnome-boxes
global_pid:     2965
kernel:         4.1.7-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 boxes_machine_real_disconnect_display at machine.c:1616
 #1 boxes_libvirt_machine_reconnect_display at libvirt-machine.c:1339
 #2 __lambda166_ at libvirt-machine.c:1427
 #3 ___lambda166__g_object_notify at libvirt-machine.c:1436
 #9 g_object_notify_by_spec_internal at gobject.c:1149
 #10 g_object_notify at gobject.c:1197
 #14 g_signal_emit_by_name at gsignal.c:3401
 #15 domain_event_cb at libvirt-gobject-connection.c:358
 #16 virDomainEventDispatchDefaultFunc at conf/domain_event.c:1345
 #17 virObjectEventStateDispatchCallbacks at conf/object_event.c:722
Comment 1 chanueting 2015-09-30 12:39:25 UTC 
Created attachment 1078619 [details]
File: backtrace
Comment 2 chanueting 2015-09-30 12:39:27 UTC 
Created attachment 1078620 [details]
File: cgroup
Comment 3 chanueting 2015-09-30 12:39:29 UTC 
Created attachment 1078621 [details]
File: core_backtrace
Comment 4 chanueting 2015-09-30 12:39:31 UTC 
Created attachment 1078622 [details]
File: dso_list
Comment 5 chanueting 2015-09-30 12:39:33 UTC 
Created attachment 1078624 [details]
File: environ
Comment 6 chanueting 2015-09-30 12:39:34 UTC 
Created attachment 1078625 [details]
File: limits
Comment 7 chanueting 2015-09-30 12:39:37 UTC 
Created attachment 1078626 [details]
File: maps
Comment 8 chanueting 2015-09-30 12:39:39 UTC 
Created attachment 1078627 [details]
File: mountinfo
Comment 9 chanueting 2015-09-30 12:39:40 UTC 
Created attachment 1078628 [details]
File: namespaces
Comment 10 chanueting 2015-09-30 12:39:42 UTC 
Created attachment 1078629 [details]
File: open_fds
Comment 11 chanueting 2015-09-30 12:39:44 UTC 
Created attachment 1078630 [details]
File: proc_pid_status
Comment 12 chanueting 2015-09-30 12:39:46 UTC 
Created attachment 1078631 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:03:57 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.