After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676301 - Boxes froze when trying to remove an unresponsive 'box'
Boxes froze when trying to remove an unresponsive 'box'
Status: RESOLVED INCOMPLETE
Product: gnome-boxes
Classification: Applications
Component: general
3.4.x (unsupported)
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-05-18 09:55 UTC by Vitezslav Humpa
Modified: 2016-03-31 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot of frozen Boxes. (18.42 KB, image/png)
2012-05-18 09:55 UTC, Vitezslav Humpa 		Details

Description Vitezslav Humpa 2012-05-18 09:55:23 UTC 
Created attachment 214297 [details]
Screenshot of frozen Boxes.

After experiencing https://bugzilla.gnome.org/show_bug.cgi?id=676299, I've attempted to remove the unresponsive F17 Beta Live guest. Boxes became unresponsive after pressing the removal button.

gnome-boxes-3.4.2-1.fc17.x86_64
qemu-kvm-1.0-17.fc17.x86_64

Screenshot attached.
Comment 1 Vitezslav Humpa 2012-05-18 10:53:10 UTC 
This is the last output I got:

(gnome-boxes:12869): Boxes-WARNING **: libvirt-machine.vala:261: Fetching of stats for 'Fedora 17' is taking too long. Probably a libvirt bug.

(gnome-boxes:12869): Clutter-WARNING **: The actor 'ClutterBox' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not recommended
Window manager warning: Attempt to perform window operation 1 on window 0x2e0000b (Boxes) when operation 1 on 0x2e0000b (Boxes) already in effect
Comment 2 Zeeshan Ali 2012-05-19 18:00:42 UTC 
Most probably its a libvirt hang. If you could reproduce it, please check if libvirt is hung by running `virsh list`.
Comment 3 Marc-Andre Lureau 2012-09-03 12:51:15 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!