Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#67362 - [virtualbox-guest-utils] vboxdrmclient.service starts too soon?

Attached to Project: Community Packages
Opened by Frank Vanderham (twelveeighty) - Wednesday, 22 July 2020, 16:16 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 22 July 2020, 20:22 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


This may be an upstream issue, or could this be a problem with virtualbox-guest-utils depending on xf86-video-vmware?

Problem: VMSVGA window resizing does not work for virtualbox-guest-utils 6.1.12-2 under X.

Journal has:

Jul 22 08:47:19 archdev1 systemd[1]: Condition check resulted in VirtualBox Guest VMSVGA resize client being skipped.

systemctl status vboxdrmclient:
* vboxdrmclient.service - VirtualBox Guest VMSVGA resize client
Loaded: loaded (/usr/lib/systemd/system/vboxdrmclient.service; static; vendor preset: disabl>
Active: inactive (dead)
Condition: start condition failed at Wed 2020-07-22 10:00:54 MDT; 54s ago
└─ ConditionPathExistsGlob=/dev/dri/renderD* was not met

But that path *does* exist by the time I can log in (X has not yet started):

$ ls /dev/dri/renderD*

A workaround is to manually start /usr/bin/VBoxDRMClient after login (before or even after starting X seems to work).

This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 22 July 2020, 20:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox 6.1.12-3
Comment by Frank Vanderham (twelveeighty) - Wednesday, 22 July 2020, 16:20 GMT
Sorry - I should have mentioned that manually removing the ConditionPathExistsGlob in vboxdrmclient.service to force it to load does not work. I guess it's a timing issue where the service is launched too soon?