I've the impression this is due to nautilus not being properly resized when display size changes (in a VM) or a new one is added...
nautilus -q
and starting the filemanager again should fix this.
I've the impression this is due to nautilus not being properly resized when display size changes (in a VM) or a new one is added...
nautilus -q
and starting the filemanager again should fix this.