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 763772 - Read-only property of VNC display not always correctly saved/loaded
Read-only property of VNC display not always correctly saved/loaded
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: properties
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-03-16 17:31 UTC by Zeeshan Ali
Modified: 2016-09-20 08:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Remove set_enable_inputs () (2.83 KB, patch)
2016-04-28 07:39 UTC, Pavel Grunt 		committed Details | Review

Description Zeeshan Ali 2016-03-16 17:31:35 UTC 
Steps to reproduce:

1. Launch a box that uses VNC as it's display (to get it running)
2. Go back to overview once it's loaded.
3. Change 'Read-only' property by launching properties view via right-click menu
4. After quitting properties, re-launch the box.
5. Launch properties from topbar menu.

Your change to Read-only property is lost.

From the fact that change is remembered if you launch the properties from overview both times, I'm guessing the issue is that property is not loaded properly rather than change not saved. Anyway, needs further debugging..
Comment 1 Pavel Grunt 2016-04-28 07:39:08 UTC 
Created attachment 326917 [details] [review]
Remove set_enable_inputs ()

It is not needed, because the spice-gtk widget has enabled inputs
by default and the vnc widget gets it from its "read-only" property.
Comment 2 Zeeshan Ali 2016-04-28 13:58:31 UTC 
Thanks, pushed with log improved.