Guest additions 5.0.18 force 2D desktop on Ubuntu 12.04

[jimnms]

I just updated to VirtualBox 5.0.18 and updated the guest additions on my Ubuntu 12.04 guest. After logging out it shrinks down to a small 1024x768 window. When I log back in, I'm forced to the 2D desktop. I can resize the window, but I can't get it to use the 3D desktop anymore. Going back to 5.0.16 guest additions works fine.

[Gianlucarenzi]

It looks like the same error as myself.
Today I upgraded to the 5.0.18 (linux ubuntu mint 13 Maya) and using a Debian Wheezy x86-32bit with a kernel 3.12 custom compiled. When installing the VirtualBox Additions in the Debian Guest (running as always the sudo ./VBoxLinuxAdditions.run) it warnings with some missing headers (but they are present) and after a reboot the Mouse Integration and Xorg dynamic resolution change does not work anymore.
Reverting to the 5.0.16 and re-installing the correct 5.0.16 VBoxAdditions, throwing the same warning about the kernel headers, but at the end of the installation, after a reboot everything is working good...

Please fix.

[meiser79]

I also see a regression in 5.0.18 with Ubuntu 14.04.

The following crash dump is found in dmesg:

Code: Select all

[    7.119129] ------------[ cut here ]------------
[    7.119153] WARNING: CPU: 0 PID: 178 at /build/linux-A0LYlV/linux-3.13.0/drivers/gpu/drm/drm_crtc.c:87 drm_warn_on_modeset_not_all_locked+0x72/0x90 [drm]()
[    7.119154] Modules linked in: joydev crct10dif_pclmul crc32_pclmul snd_intel8x0(+) snd_ac97_codec ac97_bus aesni_intel snd_pcm aes_x86_64 lrw gf128mul glue_helper ablk_helper snd_page_alloc cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer vboxvideo(OX) rfcomm ttm bnep drm_kms_helper bluetooth snd drm lpc_ich serio_raw syscopyarea soundcore video sysfillrect mac_hid sysimgblt vboxguest(OX) nfsd auth_rpcgss nfs_acl binfmt_misc nfs parport_pc lockd ppdev sunrpc fscache pptp gre pppox lp parport ahci libahci psmouse
[    7.119185] CPU: 0 PID: 178 Comm: plymouthd Tainted: G           OX 3.13.0-86-generic #130-Ubuntu
[    7.119186] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[    7.119188]  0000000000000000 ffff880035db7d50 ffffffff8172a3b4 0000000000000000
[    7.119191]  0000000000000009 ffff880035db7d88 ffffffff810699bd ffff880035db1800
[    7.119193]  ffff8800d45bab58 ffff8800d45ba800 ffff880036b4a200 ffff8800d45ba8a0
[    7.119196] Call Trace:
[    7.119202]  [<ffffffff8172a3b4>] dump_stack+0x64/0x82
[    7.119205]  [<ffffffff810699bd>] warn_slowpath_common+0x7d/0xa0
[    7.119208]  [<ffffffff81069a9a>] warn_slowpath_null+0x1a/0x20
[    7.119217]  [<ffffffffa02235c2>] drm_warn_on_modeset_not_all_locked+0x72/0x90 [drm]
[    7.119222]  [<ffffffffa01e9318>] drm_fb_helper_restore_fbdev_mode+0x28/0xd0 [drm_kms_helper]
[    7.119226]  [<ffffffffa0318154>] vbox_driver_lastclose+0x34/0x50 [vboxvideo]
[    7.119233]  [<ffffffffa02188ca>] drm_lastclose+0x4a/0x1b0 [drm]
[    7.119240]  [<ffffffffa0218e50>] drm_release+0x420/0x620 [drm]
[    7.119244]  [<ffffffff811c31c4>] __fput+0xe4/0x260
[    7.119247]  [<ffffffff811c338e>] ____fput+0xe/0x10
[    7.119249]  [<ffffffff8108ac3c>] task_work_run+0xac/0xd0
[    7.119253]  [<ffffffff81014ef7>] do_notify_resume+0x97/0xb0
[    7.119256]  [<ffffffff8173b2da>] int_signal+0x12/0x17
[    7.119258] ---[ end trace 214b3751445833a0 ]---

[jimnms]

It still happens with 5.0.20.

[michael]

I would be interested to know if anything has changed with the latest 5.0 Additions test build<1>.

<1> https://www.virtualbox.org/wiki/Testbuilds

[oldium]

My virtual machine with Ubuntu 12.04, which had problem with graphics since 5.0.18, now boots correctly with official 5.0.22. So maybe it is fixed for you too.