Bug 1274321

Summary: [abrt] gnome-boxes: __lambda215_(): gnome-boxes killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Michal Nowak <mnowak>
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, 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/d011038123f6343175037d8a69b4c6356ad43015
Whiteboard: abrt_hash:7eb8ee4cccf356955e32e6a8df806be2bdc8171f;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:18:27 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 Michal Nowak 2015-10-22 13:31:03 UTC 
Version-Release number of selected component:
gnome-boxes-3.16.2-4.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: __lambda215_
executable:     /usr/bin/gnome-boxes
global_pid:     3135
kernel:         4.2.3-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __lambda215_ at app.c:1318
 #1 ___lambda215__boxes_collection_item_removed at app.c:1323
 #5 g_signal_emit_by_name at gsignal.c:3401
 #6 boxes_collection_remove_item at collection.c:507
 #7 boxes_app_delete_machine at app.c:2560
 #8 __lambda12_ at libvirt-broker.c:1312
 #9 ___lambda12__gvir_connection_domain_removed at libvirt-broker.c:1318
 #10 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102
 #11 _g_closure_invoke_va at gclosure.c:831
 #14 domain_event_cb at libvirt-gobject-connection.c:390
Comment 1 Michal Nowak 2015-10-22 13:31:12 UTC 
Created attachment 1085508 [details]
File: backtrace
Comment 2 Michal Nowak 2015-10-22 13:31:13 UTC 
Created attachment 1085509 [details]
File: cgroup
Comment 3 Michal Nowak 2015-10-22 13:31:15 UTC 
Created attachment 1085510 [details]
File: core_backtrace
Comment 4 Michal Nowak 2015-10-22 13:31:17 UTC 
Created attachment 1085511 [details]
File: dso_list
Comment 5 Michal Nowak 2015-10-22 13:31:19 UTC 
Created attachment 1085512 [details]
File: environ
Comment 6 Michal Nowak 2015-10-22 13:31:21 UTC 
Created attachment 1085513 [details]
File: limits
Comment 7 Michal Nowak 2015-10-22 13:31:24 UTC 
Created attachment 1085514 [details]
File: maps
Comment 8 Michal Nowak 2015-10-22 13:31:26 UTC 
Created attachment 1085515 [details]
File: mountinfo
Comment 9 Michal Nowak 2015-10-22 13:31:27 UTC 
Created attachment 1085516 [details]
File: namespaces
Comment 10 Michal Nowak 2015-10-22 13:31:29 UTC 
Created attachment 1085517 [details]
File: open_fds
Comment 11 Michal Nowak 2015-10-22 13:31:31 UTC 
Created attachment 1085518 [details]
File: proc_pid_status
Comment 12 Michal Nowak 2015-10-22 13:31:33 UTC 
Created attachment 1085519 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:18:27 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.