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 751728 - Closing properties window, suspends the VM if running in secondary window
Closing properties window, suspends the VM if running in secondary window
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.16.x
Other Linux
: Normal major
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-06-30 13:51 UTC by Stephen
Modified: 2016-09-20 08:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stephen 2015-06-30 13:51:44 UTC 
To reproduce:

* Open the VM in a new window (from the hamburger menu or from the VMs overview)
* Go to the overview window, right-click VM -> Properties
* Close Properties window

Actual results:

* Secondary window showing VM goes blank.
* After exactly 60 seconds, the secondary window closes, and the VM starts suspending.

Expected results:

* Properties windows closes; nothing else happens.
Comment 1 Zeeshan Ali 2015-07-13 18:58:32 UTC 
commit: e5d0f6f391480972056d3823cd6c839ff76054d5

    app-window: Set state only on own machines
    
    If we unconditionally forward state change event to current machine from
    AppWindow, state changes from one window end up in another. This patches
    fixes this by checking if machine's window is the same as the window
    that is about to forward it's state change to the machine.