Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#44080 - [virtualbox-guest-utils] PLEASE ENTER SUMMARY

Attached to Project: Community Packages
Opened by Raphaël R. (raphaelr) - Saturday, 07 March 2015, 11:36 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 March 2015, 04:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since version 4.3.22, my Archlinux guest are unable to use xrand and dual screen correctly.

$ xrandr --output VBOX1 --right-of VBOX0
warning: output VBOX1 not found; ignoring

There is only 2 screen called VBX in display control panel of XFCE.



I've also noticed that VBoxClient aren't launched at the same way in 4.3.20 and prior:

In 4.3.20, ps -ejH give:
...
390 387 387 ? 00:00:00 VBoxClient
402 399 399 ? 00:00:00 VBoxClient
407 404 404 ? 00:00:00 VBoxClient
411 410 410 ? 00:00:00 VBoxClient

In 4.3.22 or 4.3.24:
...
519 518 518 ? 00:00:00 VBoxClient
521 518 518 ? 00:00:00 VBoxClient
531 530 530 ? 00:00:00 VBoxClient
533 530 530 ? 00:00:00 VBoxClient
538 537 537 ? 00:00:00 VBoxClient
540 537 537 ? 00:00:00 VBoxClient
546 545 545 ? 00:00:00 VBoxClient
547 545 545 ? 00:00:00 VBoxClient

There is "child process" now.

Additional info:

virtualbox-guest-modules 4.3.24-1
virtualbox-guest-modules-lts 4.3.24-1
virtualbox-guest-utils 4.3.24-1

I've seen that a virtualbox-guest-utils 4.3.24-2 is on the svn, but I'm not able to catch it despite using one of the most up to date mirror ( archlinux.polymorf.fr )


Steps to reproduce:
Just install VirtualBox guest and using a Desktop Environment like XFCE.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 08 March 2015, 04:48 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Saturday, 07 March 2015, 15:04 GMT
What's the output of just running xrandr without any arguments?
Comment by Raphaël R. (raphaelr) - Saturday, 07 March 2015, 15:24 GMT
With 4.3.24 guest and modules

$ xrandr
Screen 0: minimum 64 x 64, current 1920 x 1050, maximum 16384 x 16384
VGA-0 connected 1920x1050+0+0 0mm x 0mm
1920x1050 60.00*+
1600x1200 60.00
1440x1050 60.00
1280x960 60.00
1024x768 60.00
800x600 60.00
640x480 60.00
VGA-1 connected 1680x1020+0+0 0mm x 0mm
1680x1020 60.00*+
1600x1200 60.00
1440x1050 60.00
1280x960 60.00
1024x768 60.00
800x600 60.00
640x480 60.00
Comment by Doug Newgard (Scimmia) - Saturday, 07 March 2015, 15:35 GMT
So the names appear to be VGA-0 and VGA-1, not VBOX0 and VBOX1.
Comment by Raphaël R. (raphaelr) - Saturday, 07 March 2015, 15:49 GMT
Yep, but on a VM with VirtualBox 4.3.20 guest utils and modules :

$ xrandr
Screen 0: minimum 64 x 64, current 3600 x 1050, maximum 16384 x 16384
VBOX0 connected 1920x1050+0+0 0mm x 0mm
1920x1050 60.00*+
1440x1050 60.00
1280x960 60.00
1024x768 60.00
800x600 60.00
640x480 60.00
VBOX1 connected 1680x1020+1920+0 0mm x 0mm
1680x1020 60.00*+
1440x1050 60.00
1280x960 60.00
1024x768 60.00
800x600 60.00
640x480 60.00

Comment by Doug Newgard (Scimmia) - Saturday, 07 March 2015, 17:27 GMT
OK, so the names changed in a version update, how is that a bug?
Comment by Raphaël R. (raphaelr) - Saturday, 07 March 2015, 19:14 GMT
As each VBoxClient haved changed, now they have child, used twice of memory and name of screen under Vbox have changed, I though there a bug since 4.3.22 in guest-utils.

Calling xrandr --output VGA-1 --right-of VGA-0 works like previously

Digging a little more lead me to https://www.virtualbox.org/ticket/13287 so it seems this change is normal en 4.3.22. Sorry for the noise :(

Loading...