Gnome-boxes dumps core on start

Bug #1245086 reported by Roel Brook
10
This bug affects 2 people
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/modules/.
p11-kit: couldn't read config file: /usr/share/p11-kit/modules/.

** (gnome-boxes:25984): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-boxes:25984): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed
Segmentation fault (core dumped)

All checks the program provides return success.

$ gnome-boxes --checks

(gnome-boxes:28221): Boxes-WARNING **: util-app.vala:247: Failed to execute child process "restorecon" (No such file or directory)
• 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://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>.
Boxes home page: <http://live.gnome.org/Boxes>.
$ virsh -c qemu:///session pool-dumpxml gnome-boxes
p11-kit: invalid config filename, will be ignored in the future: /usr/share/p11-kit/modules/.
p11-kit: couldn't read config file: /usr/share/p11-kit/modules/.
<pool type='dir'>
  <name>gnome-boxes</name>
  <uuid>b9f4f520-d857-48e9-aae3-e4656ae5fb7e</uuid>
  <capacity unit='bytes'>350211670016</capacity>
  <allocation unit='bytes'>131072</allocation>
  <available unit='bytes'>350211538944</available>
  <source>
  </source>
  <target>
    <path>/sub/boxes</path>
    <permissions>
      <mode>0744</mode>
      <owner>1000</owner>
      <group>1000</group>
    </permissions>
  </target>
</pool>

I will attach the coredump.

The same issue is reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=999957

Revision history for this message
Roel Brook (rainmaker52) wrote :
Revision history for this message
Roel Brook (rainmaker52) wrote :

OK, semi fixed.

I did the following:
- Remove the pool using virsh
- rm -r ~/.local/share/gnome-boxes
- 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.

Changed in gnome-boxes (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.