Gnome-boxes dumps core on start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-boxes (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
gnome-boxes (openSUSE) |
New
|
Undecided
|
Unassigned |
Bug Description
After starting gnome-boxes, after the window is drawn, gnome-boxes crashes with a core-dump.
The following output is displayed in the terminal:
$ gnome-boxes
p11-kit: invalid config filename, will be ignored in the future: /usr/share/
p11-kit: couldn't read config file: /usr/share/
** (gnome-
(gnome-
Segmentation fault (core dumped)
All checks the program provides return success.
$ gnome-boxes --checks
(gnome-
• The CPU is capable of virtualization: yes
• The KVM module is loaded: yes
• Libvirt KVM guest available: yes
• Boxes storage pool available: yes
• The SELinux context is default: no
Report bugs to <https:/
Boxes home page: <http://
$ virsh -c qemu:///session pool-dumpxml gnome-boxes
p11-kit: invalid config filename, will be ignored in the future: /usr/share/
p11-kit: couldn't read config file: /usr/share/
<pool type='dir'>
<name>
<uuid>
<capacity unit='bytes'
<allocation unit='bytes'
<available unit='bytes'
<source>
</source>
<target>
<path>
<permissions>
<
<
<
</permissions>
</target>
</pool>
I will attach the coredump.
The same issue is reported on Fedora: https:/
OK, semi fixed.
I did the following: share/gnome- boxes
- Remove the pool using virsh
- rm -r ~/.local/
- reset all dconf values to their default
- Reinstall gnome-boxes
Skipping either the dconf or the ~/.local/ share/gnome- boxes folder resulted in the exact same segfault.
Marking this one as fixed, as it seems to have been a local problem.