Unable to resize any window on my linux host after starting virtualbox running windows guest
Posted: 20. Aug 2016, 14:13
Host: Ubuntu 14.04 LTS, 16Gb ram, 64 bit kernel, running latest Unity desktop.
Guest: Windows 7 given 7 gig of ram with Guest Additions 5.0.26 installed
VritualBox: 5.0.26 r108824
I don't use any fancy windowing features on my linux machine, it's a vanilla Ubuntu 14.04 Unity desktop. Before I run virtualbox, I can resize any window on the host as you would expect (drag window edges, hold alt and drag middle mouse button, and maximise/unmaximise normally).
After running VB, I find I cannot resize host windows, except to maximise/unmaximise. So if I left a text editor like Sublime or gedit at a certain size, it cannot be changed by dragging the window edge or the alt+middle mouse trick. Windows can be maximised but this gets very annoying very quickly.
I see nothing useful in syslog about this. I don't know how to debug this, and googling the problem just find me posts about resizing desktop resolutions or hard drives, nothing about the host system's window manager problems.
See VB log file for this guest's startup attached. Any ideas how to approach this?
Thanks, Nick
Guest: Windows 7 given 7 gig of ram with Guest Additions 5.0.26 installed
VritualBox: 5.0.26 r108824
I don't use any fancy windowing features on my linux machine, it's a vanilla Ubuntu 14.04 Unity desktop. Before I run virtualbox, I can resize any window on the host as you would expect (drag window edges, hold alt and drag middle mouse button, and maximise/unmaximise normally).
After running VB, I find I cannot resize host windows, except to maximise/unmaximise. So if I left a text editor like Sublime or gedit at a certain size, it cannot be changed by dragging the window edge or the alt+middle mouse trick. Windows can be maximised but this gets very annoying very quickly.
I see nothing useful in syslog about this. I don't know how to debug this, and googling the problem just find me posts about resizing desktop resolutions or hard drives, nothing about the host system's window manager problems.
See VB log file for this guest's startup attached. Any ideas how to approach this?
Thanks, Nick