GNOME Bugzilla – Bug 729168
Don't automatically fullscreen boxes on launching them
Last modified: 2016-03-31 13:22:07 UTC
At the moment there's no way to prevent fullscreening every time a VM is launched. This means if a user prefers to run a VM in gnome-boxes maximised but not fullscreened, they have to un-fullscreen it on every launch. Please provide an option for this (per-VM?), a dconf key or remember the last state for each VM. The fullscreen state is also not remembered when switching back from the VM settings - when switching from a non-fullscreen VM to its settings, on switch-back gnome-boxes goes fullscreen again.
Talked to jimmac about this for a bit and he told me that the current design of going fullscreen by default is being rethought and its likely to be phased-out. So I'll keep this open for that. About having an option, no this is not exactly a setting but more about doing what user wants us to do.
(In reply to comment #0) > > The fullscreen state is also not remembered when switching back from the VM > settings - when switching from a non-fullscreen VM to its settings, on > switch-back gnome-boxes goes fullscreen again. Can you still reproduce this part? I can't.
(In reply to comment #2) > (In reply to comment #0) > > > > The fullscreen state is also not remembered when switching back from the VM > > settings - when switching from a non-fullscreen VM to its settings, on > > switch-back gnome-boxes goes fullscreen again. > > Can you still reproduce this part? I can't. If you can, please file it under a new bug.
Has the main part of fullscreen on launch been changed/fixed? You had said this bug was going to be kept open for that? Still seeing the fullscreen-on-settings-exit part as well.
(In reply to comment #4) > Has the main part of fullscreen on launch been changed/fixed? You had said this > bug was going to be kept open for that? Yes, in git master. > Still seeing the fullscreen-on-settings-exit part as well. I can reproduce this after reverting my "Don't fullsceeen on launch" patch so I guess this got fixed with it.
(In reply to comment #5) > > Still seeing the fullscreen-on-settings-exit part as well. > > I can reproduce this after reverting my "Don't fullsceeen on launch" patch so I > guess this got fixed with it. Since "Don't fullsceeen on launch" is a UI change, I can't push that to stable branch so I fixed the fullscreen-on-settings-exit only in 3.12. It'll be shortly released in 3.12.2.
Sorry, found another path to unwanted fullscreening - when viewing a VM maximised/non-fullscreen, click the back button in the top left corner to return to the VMs overview, then click the VM again, and it gets fullscreened.
(In reply to comment #7) > Sorry, found another path to unwanted fullscreening - when viewing a VM > maximised/non-fullscreen, click the back button in the top left corner to > return to the VMs overview, then click the VM again, and it gets fullscreened. Are we talking 3.13 branch? Cause I haven't fixed this in 3.12 as thats a UI change, which is not allowed in stable branch.
3.12; has it been changed in 3.13? For clarity: Fullscreen on VM start: fixed in 3.13.x according to this bug, wontfix in 3.12.x Fullscreen on return from VM settings: fixed in 3.12.x Fullscreen on return from VM list (my #7 above): not fixed in 3.13.x? Not fixed in 3.12.x I'd contend that the last is on the same level as the 2nd, 3.12.x-fixed issue; a bug and not a feature/behaviour choice, and so also eligible for 3.12.x bugfix release?
(In reply to comment #9) > 3.12; has it been changed in 3.13? Yes. > Fullscreen on VM start: fixed in 3.13.x according to this bug, wontfix in > 3.12.x > Fullscreen on return from VM settings: fixed in 3.12.x Yes. > Fullscreen on return from VM list (my #7 above): not fixed in 3.13.x? Not fixed > in 3.12.x That is not any different from launching for the first time and therefore same as this bug. > I'd contend that the last is on the same level as the 2nd, 3.12.x-fixed issue; > a bug and not a feature/behaviour choice, and so also eligible for 3.12.x > bugfix release? Its not a bug, it's a feature we decided is not a good idea and hence reverted.