Ticket #5687 (closed defect: obsolete)
Screen size does not auto-adjust with openSUSE 11.2 as guest
Reported by: | DiskCrasher | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 3.0.12 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
The 11.1 RPMs appear to install correctly in openSUSE 11.2 but there is at least one issue when adjusting the screen size. Often when the VirtualBox host window is resized, the openSUSE guest screen size is not automatically adjusted even though Auto-resize Guest Display is selected. If I go into Configure Display within the openSUSE guest and select 1280x901 (Auto) it usually works, but after changing VBox host window size (e.g. switch from full screen to tiled) it switches back to some other resolution in openSUSE and does not auto-resize anymore. Very annoying bug that did not exist in 11.1. Vista x64 is the host OS.
Attachments
Change History
comment:1 Changed 13 years ago by DiskCrasher
When I say the RPMs install correctly I mean to say that VBox guest additions installs correctly in openSUSE 11.2 (as guest).
comment:2 Changed 13 years ago by michael
I take it that by the RPMs, you mean the Additions installation script? Or do you mean a third-party Additions package? At least under Gnome, I know that selecting a resolution via the guest GUI can cause problems with auto-resize - the guest always forces the resolution back to whatever you chose, and our auto-resize code does not insist. Might you be seeing something similar?
Please also provide the output of the xrandr command in the guest.
comment:3 Changed 13 years ago by DiskCrasher
Yes, I mean the guest additions script that comes with VBox. I'm using KDE. This problem didn't exist with openSUSE 11.1.
comment:4 Changed 13 years ago by joekrahn
Auto-resize was working for me until I upgraded from 3.0.11 to 3.0.12. I am running Fedora 11 32-bit in Vista 64-bit. it would be nice if VboxClient had a debug option so you could distinguish host resize message failure versus xrandr problems. (Or maybe --nodaemon does that already?)
Tonight, I will try switching back to vbox 3.0.11 to see if that is in fact the problem, and not just a coincidence with some other guest OS update.
comment:5 Changed 13 years ago by joekrahn
About my previous comment: it was actually an upgrade from 3.0.8 to 3.0.12. I re-installed the vbox additions, and my system now works fine.
One thing to be aware of is that auto-resize is managed by "/usr/bin/VBoxClient --autoresize", which should run when you log in.
comment:6 Changed 10 years ago by frank
- Status changed from new to closed
- Resolution set to obsolete
comment:7 follow-up: ↓ 8 Changed 7 years ago by Richlv
if somebody stumbles upon this old thread, in the latest virtualbox versions the command is "/usr/bin/VBoxClient --display" - although if it should probably work auto of the box in many distros anyway.
comment:8 in reply to: ↑ 7 Changed 3 years ago by Delvien
Replying to Richlv:
if somebody stumbles upon this old thread, in the latest virtualbox versions the command is "/usr/bin/VBoxClient --display" - although if it should probably work auto of the box in many distros anyway.
--vmsvga instead of --display if you are using 3d acceleration (have not tested with 3d acceleration off, however)