This is the background task that supports automatic display resizing in a VirtualBox guest when using the VMSVGA display controller. Both autostart and manually starting from the command line fail in the same way. dmesg shows [ 247.553285] Service: Display SVGA X11 [ 247.579050] Starting DRM client. [ 247.580820] execve for eturns the following error -1079741204 <NULL> [ 248.047518] Running service failed: VERR_NOT_AVAILABLE The error number is different every time, so is probably meaningless.
Note this is the same error that occurs when running 'VBoxClient --vmsvga' when using GNOME on Wayland. It appears that on 64-bit systems VBoxClient use the old X11-only method but on 32-bit systems it uses the new DRM method.
Thank you for another learned report. Can you confirm: - 32-bit VB host running a 32-bit client ? Again it seems best to give this directly to tmb.
Assignee: bugsquad => tmb
(In reply to Lewis Smith from comment #2) > Thank you for another learned report. Can you confirm: > - 32-bit VB host running a 32-bit client ? > There is no 32bit host anymore, only 64bit
please try with virtualbox-6.1.16-12.mga8 it provides VBoxDRMClient and systemd integration
No joy. vmboxdrmclient.service is a static service, and there doesn't seem to be anything that enables it. I had a quick look at the Fedora package, and they have a udev rule to do that - tried adding it to vbox-additions to rules, but it didn't help. I'll have another look tomorrow when I'm less tired. You also seem to have lost the startup of the other VBoxClient services.
if you enable it manually and reboot, does it work then ? the problem is that presets only trigger on package install, not updates... I will add more triggers tomorrow to fix upgrade path
Nope, you can't enable it because it is a static service (not Wanted by anything). Manually starting it does work.
(In reply to Martin Whitaker from comment #7) > Nope, you can't enable it because it is a static service (not Wanted by > anything). Ah, indeed... I'll think about if/how to handle it tomorrow... > > Manually starting it does work. And the auto-resizing work ?
Yes, once started, auto-resizing worked.
(In reply to Martin Whitaker from comment #9) > Yes, once started, auto-resizing worked. great, then I should be able to fix it up tomorrow... I'm way too tired at this point...
please try with virtualbox-6.1.16-14.mga8
Yes, that fixes the auto-resizing - and it now works on the DM login screen as well which is a bonus. We need to run /usr/bin/VBoxClient --clipboard /usr/bin/VBoxClient --checkhostversion /usr/bin/VBoxClient --seamless /usr/bin/VBoxClient --draganddrop manually though. I guess they still need to be part of the user session startup.
virtualbox-6.1.16-15.mga8 currently building should hopefylly resolve the last missing bits.
Works for me.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED