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 674614 - gnome-boxes freezes when shutting down guest system
gnome-boxes freezes when shutting down guest system
Status: RESOLVED DUPLICATE of bug 676214
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-04-23 10:25 UTC by Christophe Fergeau
Modified: 2016-03-31 13:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christophe Fergeau 2012-04-23 10:25:19 UTC
From https://bugzilla.redhat.com/show_bug.cgi?id=815095 :

w_pirker 2012-04-22 09:28:37 EDT

Description of problem:
after shutting down the guest system (Tiny Core was used as guest), gnome-boxes
doesn't respond anymore. 

Version-Release number of selected component (if applicable):
gnome-boxes version: 
gnome-boxes version: 3.4.1
gtk3 version: 3.4.1

Steps to Reproduce:
1. yum install gnome-boxes
2. if necessary allow access to write log files at /var/log/audit/audit.log
(because of Bug 815078)
3. following media was used to produce this error:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/TinyCore-current.iso
4. boot Tiny Core and when it is booted click on the left button in it's panel
to shut it down.

Actual results:
gnome-boxes doesn't respond anymore, it's frozen. 

If started from terminal it shows: "(gnome-boxes:27744): Gtk-CRITICAL **:
_gtk_widget_captured_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget,
event)' failed"

Additional info:
I also tested it with another guest (Windows XP), where it didn't happen.


Comment 1 Christophe Fergeau 2012-04-23 06:04:29 EDT

I can reproduce it with the 3.4 branch from git, will forward upstream
Comment 1 Christophe Fergeau 2012-06-08 10:08:41 UTC
Let's say it's the same as #676214

*** This bug has been marked as a duplicate of bug 676214 ***