Description of problem: The crash just happens as soon as I run gnome-boxes. See the command-line output below. I cannot reproduce this problem in the same PC using a fresh profile, so I suspect of the last steps I took before Boxes started crashing: I had interrupted boxes during the creation of a snapshot, as a result the VM became unusable (error was something like "no current snapshot"). I cloned the VM and, once I checked the cloned machine could boot, I deleted the old one. I think that was the last time I used Boxes; now I get this crash every time I run it. $ gnome-boxes (gnome-boxes:85816): Boxes-WARNING **: 13:25:54.232: shared-folders.vala:82: File exists (gnome-boxes:85816): Boxes-WARNING **: 13:25:54.232: shared-folders.vala:82: File exists (gnome-boxes:85816): Boxes-WARNING **: 13:25:54.232: shared-folders.vala:82: File exists (gnome-boxes:85816): Boxes-WARNING **: 13:25:54.232: shared-folders.vala:82: File exists (gnome-boxes:85816): Gtk-WARNING **: 13:25:54.394: GtkFlowBox with a model will ignore sort and filter functions (gnome-boxes:85816): Gtk-WARNING **: 13:25:54.395: GtkListBox with a model will ignore sort and filter functions (gnome-boxes:85816): Boxes-WARNING **: 13:25:55.075: libvirt-machine.vala:83: Failed to disable 3D Acceleration (gnome-boxes:85816): Boxes-WARNING **: 13:25:55.077: libvirt-broker.vala:70: Failed to update domain 'win10-2': Failed to set domain configuration: XML error: Invalid PCI address 0000:04:00.0. slot must be >= 1 (gnome-boxes:85816): Boxes-CRITICAL **: 13:25:55.078: boxes_vm_importer_get_source_media: assertion 'self != NULL' failed Segmentation fault (core dumped) Version-Release number of selected component: gnome-boxes-3.38.2-1.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.Boxes.SearchProvider.slice/dbus-:1.2-org.gnome.Boxes.SearchProvider cmdline: gnome-boxes --open-uuid 96f91a82-6c27-4ca3-ab47-2a11593bd7d5 crash_function: boxes_libvirt_broker_real_add_source_co.isra.0 executable: /usr/bin/gnome-boxes journald_cursor: s=40ffcb3fd19842f5a0963a26da1d7834;i=cb35;b=59a4adda25884077ad7b8e539de38fa0;m=aa22c0835;t=5b860ff3ed03e;x=e4c7ee7bc05e4a13 kernel: 5.9.16-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 boxes_libvirt_broker_real_add_source_co.isra.0 at src/gnome-boxes.p/libvirt-broker.c:1804 #1 g_task_return_now at ../gio/gtask.c:1215 #2 g_task_return at ../gio/gtask.c:1285 #3 boxes_libvirt_broker_try_add_existing_domain_co.isra.0 at src/gnome-boxes.p/libvirt-broker.c:1409 #4 g_task_return_now at ../gio/gtask.c:1215 #5 g_task_return at ../gio/gtask.c:1285 #6 boxes_libvirt_broker_add_domain_co at src/gnome-boxes.p/libvirt-broker.c:1128 #7 g_task_return_now at ../gio/gtask.c:1215 #8 complete_in_idle_cb at ../gio/gtask.c:1229 #12 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4119
Created attachment 1745615 [details] File: backtrace
Created attachment 1745616 [details] File: core_backtrace
Created attachment 1745617 [details] File: cpuinfo
Created attachment 1745618 [details] File: dso_list
Created attachment 1745619 [details] File: environ
Created attachment 1745620 [details] File: exploitable
Created attachment 1745621 [details] File: limits
Created attachment 1745622 [details] File: maps
Created attachment 1745623 [details] File: mountinfo
Created attachment 1745624 [details] File: open_fds
Created attachment 1745625 [details] File: proc_pid_status
Created attachment 1745626 [details] File: var_log_messages
An update: I checked the configuration file of the cloned VM, in my case it was: .config/libvirt/qemu/win10-2.xml I noticed that the path in this part of the config file was wrong and I updated it: <domain type='kvm'> <name>win10-2</name> <uuid>96f91a82-6c27-4ca3-ab47-2a11593bd7d5</uuid> <title>Microsoft Windows 10 2</title> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://microsoft.com/win/10"/> </libosinfo:libosinfo> <boxes:gnome-boxes xmlns:boxes="https://wiki.gnome.org/Apps/Boxes"> <os-state>libvirt-cloning</os-state> <media>/home/jaragunde/.local/share/gnome-boxes/images/win10</media> <- THIS IS THE OLD PATH </boxes:gnome-boxes> ... Now, the error is different; there is no crash, but boxes says it "cannot access the virtualization backend". This shows up in the journal: ene 11 12:21:40 shy-guy libvirtd[108500]: internal error: pool has no config file ene 11 12:21:40 shy-guy libvirtd[108500]: ignoring dangling symlink '/home/jaragunde/.local/share/gnome-boxes/images/win7-ultimat' ene 11 12:21:40 shy-guy libvirtd[108500]: ignoring dangling symlink '/home/jaragunde/.local/share/gnome-boxes/images/win7-ultimat' ene 11 12:21:40 shy-guy libvirtd[108500]: operation failed: pool 'gnome-boxes' already exists with uuid 08755f3d-eaf4-4e65-9ff2-b0f3ebc72ea8 ene 11 12:21:40 shy-guy libvirtd[108500]: hostname: shy-guy ene 11 12:21:40 shy-guy libvirtd[108500]: libvirt version: 6.6.0, package: 5.fc33 (Fedora Project, 2020-12-07-17:58:21, )
*** Bug 1927048 has been marked as a duplicate of this bug. ***
*** Bug 1940092 has been marked as a duplicate of this bug. ***
*** Bug 1953363 has been marked as a duplicate of this bug. ***
Similar problem has been detected: automatic retrace failed on my computer at 184.68.109.94,I killed a user session with -w -ABRT but this application was closed along time ago and I didnt launch any of the virtual machines that I can recall. it also restarted from 0% downloaded several times whaen downloading the debug info's. I am also unable to login graphically now, I tryed to change the hostname sometime yesterday but after a restart it changed back reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1002.slice/user/dbus\x2d:1.2\x2dorg.gnome.Boxes.slice/dbus-:1.2-org.gnome.Boxes cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_libvirt_broker_real_add_source_co.isra.0 executable: /usr/bin/gnome-boxes journald_cursor: s=6a0eb8557605488098db6c3d9300d12f;i=34c4b;b=13c4f4da8fd640b7a4841eefff7892bc;m=2f5df8e6;t=5c14a4274ae0d;x=621652a5a8f4f0a0 kernel: 5.11.14-200.fc33.x86_64 package: gnome-boxes-3.38.2-2.fc33 reason: gnome-boxes killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1002
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.