Version-Release number of selected component: gnome-boxes-3.16.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: vasprintf executable: /usr/bin/gnome-boxes global_pid: 24295 kernel: 4.0.1-300.fc22.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 vasprintf at /usr/include/bits/stdio2.h:210 #4 g_vasprintf at gprintf.c:316 #5 g_strdup_vprintf at gstrfuncs.c:507 #8 gvir_event_handle_update at libvirt-glib-event.c:231 #9 virNetSocketUpdateIOCallback at rpc/virnetsocket.c:1908 #10 virNetClientIOUpdateCallback at rpc/virnetclient.c:1635 #11 virNetClientIO at rpc/virnetclient.c:1783 #12 virNetClientSendInternal at rpc/virnetclient.c:1958 #13 virNetClientSendWithReply at rpc/virnetclient.c:1986 #14 virNetClientProgramCall at rpc/virnetclientprogram.c:329
Created attachment 1024022 [details] File: backtrace
Created attachment 1024023 [details] File: cgroup
Created attachment 1024024 [details] File: core_backtrace
Created attachment 1024025 [details] File: dso_list
Created attachment 1024026 [details] File: environ
Created attachment 1024027 [details] File: limits
Created attachment 1024028 [details] File: maps
Created attachment 1024029 [details] File: mountinfo
Created attachment 1024030 [details] File: namespaces
Created attachment 1024031 [details] File: open_fds
Created attachment 1024032 [details] File: proc_pid_status
Created attachment 1024033 [details] File: var_log_messages
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.