Opened 5 years ago
Last modified 5 years ago
#18098 new defect
Screen does not refresh when connecting over RDP
| Reported by: | oddsocks | Owned by: | |
|---|---|---|---|
| Component: | guest additions/x11/graphics | Version: | VirtualBox 5.2.20 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
With Guest Additions 5.2.20 installed and the guest running Fedora Linux, when connecting via RDP the screen does not get refreshed when running the graphical environment. It gives the impression the guest has hung but that isn't the case. If you reconnect then the screen is updated but once again no longer refreshes.
So far this occurs both under Fedora 28 and Fedora 29 guests. I will check with other versions of Linux and other OSs as time allows.
If I downgrade the guest additions to 5.2.18 then the issue goes away. If I uninstall the guest additions then the display also works as expected but obviously without the advantages of having guest additions installed.
Attachments (1)
Change History (6)
by , 5 years ago
| Attachment: | f29-vbox.log.bz2 added |
|---|
comment:1 by , 5 years ago
Windows guests do not seem to be affected, however Ubuntu 18.04 is affected in the same way so it's not specific to Fedora.
follow-up: 5 comment:2 by , 5 years ago
VirtualBox VM 5.2.20 r125813 linux.amd64 (Oct 15 2018 17:11:04) release log
5.2.22 is out, and you might want to try the 5.2.23 test builds as well. You are using the latest and greatest Fedora after all... If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox.
00:00:00.054518 VRamSize <integer> = 0x0000000000a00000 (10 485 760, 10 MB)
You might want to take the VRAM to 32, 64 or even 128 MB in the VM Settings » Display. What if you enable 3D acceleration at the same place? Does that change the situation?
BTW, It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
comment:3 by , 5 years ago
A couple more things you might try: the VMSVGA graphics device in 6.0.0, and seeing if the Additions components provided by Ubuntu/Fedora (what is there before you install the Additions manually) work better.
comment:4 by , 5 years ago
Thanks Michael. The issue still persists in VB 6.0.0 but it seems to be specifically related to Wayland. If I force GDM to use Xorg then there's no problem with the VB 6.0.0 guest additions being installed. The issue still persists if Wayland is used. I'm not sure why Wayland wasn't a problem before.
comment:5 by , 5 years ago
5.2.22 is out, and you might want to try the 5.2.23 test builds as well. You are using the latest and greatest Fedora after all... If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox.
It was the latest when I opened the bug and I've tried every version since, without change.
You might want to take the VRAM to 32, 64 or even 128 MB in the VM Settings » Display. What if you enable 3D acceleration at the same place? Does that change the situation?
I didn't see why that would make a difference, and FWIW it doesn't. Have you checked it yourself? The VM is running on a headless server so no 3D acceleration.
BTW, It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
For sure, but if this is a bug shouldn't it be reported? I get that a workaround = useful, but that's not the same as bug = fixed. Thanks for your help
VBox Log file from a Fedora 29 guest