Bug 815095 - gnome-boxes freezes when shutting down guest system
gnome-boxes freezes when shutting down guest system
Product: Fedora
Classification: Fedora
Component: gnome-boxes (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Christophe Fergeau
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-22 09:28 EDT by Wolfgang Pirker
Modified: 2013-07-31 18:07 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 18:07:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wolfgang 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:
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 2 Christophe Fergeau 2012-04-23 06:26:23 EDT
Filed as https://bugzilla.gnome.org/show_bug.cgi?id=674614
Comment 3 Fedora End Of Life 2013-07-03 17:12:40 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.
Comment 4 Fedora End Of Life 2013-07-31 18:07:12 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.