Created attachment 783804 [details] bug demonstration video Description of problem: See the attached video. The VM window size is not remembered correctly. Its height is not remembered at all, it always appears with a default height. The width is remembered, but if the width is larger than approximately half of the screen, the window is maximized on start instead. Please remember the window size and window state (normal/maximized). Restore its size and state correctly on window open. I'm using SPICE and QXL. Version-Release number of selected component (if applicable): libvirt-1.0.5.4-1.fc19.x86_64 libvirt-client-1.0.5.4-1.fc19.x86_64 libvirt-daemon-1.0.5.4-1.fc19.x86_64 libvirt-daemon-config-network-1.0.5.4-1.fc19.x86_64 libvirt-daemon-config-nwfilter-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-interface-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-libxl-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-lxc-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-network-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-nodedev-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-nwfilter-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-qemu-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-secret-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-storage-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-uml-1.0.5.4-1.fc19.x86_64 libvirt-daemon-driver-xen-1.0.5.4-1.fc19.x86_64 libvirt-daemon-kvm-1.0.5.4-1.fc19.x86_64 libvirt-glib-0.1.6-1.fc19.x86_64 libvirt-python-1.0.5.4-1.fc19.x86_64 virt-install-0.10.0-1.fc19.noarch virt-manager-0.10.0-1.fc19.noarch virt-manager-common-0.10.0-1.fc19.noarch virt-top-1.0.8-4.fc19.x86_64 virt-viewer-0.5.6-1.fc19.x86_64 ipxe-roms-qemu-20130517-2.gitc4bce43.fc19.noarch libvirt-daemon-driver-qemu-1.0.5.4-1.fc19.x86_64 qemu-1.4.2-5.fc19.x86_64 qemu-common-1.4.2-5.fc19.x86_64 qemu-img-1.4.2-5.fc19.x86_64 qemu-kvm-1.4.2-5.fc19.x86_64 qemu-system-alpha-1.4.2-5.fc19.x86_64 qemu-system-arm-1.4.2-5.fc19.x86_64 qemu-system-cris-1.4.2-5.fc19.x86_64 qemu-system-lm32-1.4.2-5.fc19.x86_64 qemu-system-m68k-1.4.2-5.fc19.x86_64 qemu-system-microblaze-1.4.2-5.fc19.x86_64 qemu-system-mips-1.4.2-5.fc19.x86_64 qemu-system-or32-1.4.2-5.fc19.x86_64 qemu-system-ppc-1.4.2-5.fc19.x86_64 qemu-system-s390x-1.4.2-5.fc19.x86_64 qemu-system-sh4-1.4.2-5.fc19.x86_64 qemu-system-sparc-1.4.2-5.fc19.x86_64 qemu-system-unicore32-1.4.2-5.fc19.x86_64 qemu-system-x86-1.4.2-5.fc19.x86_64 qemu-system-xtensa-1.4.2-5.fc19.x86_64 qemu-user-1.4.2-5.fc19.x86_64 spice-glib-0.20-2.fc19.x86_64 spice-gtk-0.20-2.fc19.x86_64 spice-gtk3-0.20-2.fc19.x86_64 spice-gtk-python-0.20-2.fc19.x86_64 spice-server-0.12.3-1.fc19.x86_64 xorg-x11-drv-qxl-0.1.1-0.11.20130514git77a1594.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. open and close the VM window, changing its size between the attempts
Thanks for the video, but I can't reproduce either of the confusing behaviors with a fully updated F19. And in fact virt-manager doesn't do anything with changing the window size when you reopen a window, since we just hide/unhide it, all the attributes should be remembered. If you run virt-manager --debug, are there any errors on the console when reproducing? Any non-default gnome extensions or window manager tweaks that you've installed which could be the culprit?
I have found out that this is a problem of gnome-shell. Reported here with all details: https://bugzilla.gnome.org/show_bug.cgi?id=707378 Changing component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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.
Still a problem in Fedora 21. Updated upstream report.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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 this bug is closed as described in the policy above. 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Sure, still a problem.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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 this bug is closed as described in the policy above. 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.