Version-Release number of selected component: gnome-boxes-3.13.4-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_vm_creator_guest_installed_os executable: /usr/bin/gnome-boxes kernel: 3.16.1-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (9 frames) #0 boxes_vm_creator_guest_installed_os at /home/zeenix/checkout/gnome/gnome-boxes/src/vm-creator.vala:282 #1 boxes_vm_creator_on_machine_state_changed at /home/zeenix/checkout/gnome/gnome-boxes/src/vm-creator.vala:147 #2 boxes_vm_creator_real_continue_installation_co at /home/zeenix/checkout/gnome/gnome-boxes/src/vm-creator.vala:113 #3 g_simple_async_result_complete at gsimpleasyncresult.c:763 #4 complete_in_idle_cb at gsimpleasyncresult.c:775 #8 g_main_context_iteration at gmain.c:3795 #9 g_application_run at gapplication.c:2219 #10 _vala_main at /home/zeenix/checkout/gnome/gnome-boxes/src/main.vala:84 #12 _start
Created attachment 928222 [details] File: backtrace
Created attachment 928224 [details] File: cgroup
Created attachment 928225 [details] File: core_backtrace
Created attachment 928226 [details] File: dso_list
Created attachment 928227 [details] File: environ
Created attachment 928228 [details] File: exploitable
Created attachment 928229 [details] File: limits
Created attachment 928230 [details] File: maps
Created attachment 928231 [details] File: open_fds
Created attachment 928232 [details] File: proc_pid_status
Created attachment 928233 [details] File: var_log_messages
I've deleted ./config and ./local files and it happens like this too with this error (gnome-boxes:9558): Boxes-WARNING **: libvirt-broker.vala:90: Failed to start storage pool: cannot open path '/home/vbenes/.local/share/gnome-boxes/images': No such file or directory (gnome-boxes:9558): Libvirt.GObject-WARNING **: (libvirt-gobject-storage-pool.c:563):gvir_storage_pool_get_volume: code should not be reached (gnome-boxes:9558): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed Segmentation fault (core dumped)
You need to remove the gnome-boxes storage pool from libvirt as well virsh -c qemu:///session pool-list --all virsh -c qemu:///session pool-undefine gnome-boxes (maybe I'm missing some steps, but you get the idea. Let me know if this is not enough and you get stuck)
I've destroyed and undefined gnome-boxes pool but getting still the same error. Any more hints?
and deleting ~/.config/libvirt helped!
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.