Custom Query (16363 matches)
Results (2374 - 2376 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15549 | fixed | VB 5.0.22 fails to start on Solaris 10 | ||
| Description |
After upgrading to 5.0.22, attempts to start VirtualBox fail with VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/opt/VirtualBox/amd64/VirtualBox.so",) failed: ld.so.1: VirtualBox: fatal: relocation error: file /opt/VirtualBox/amd64/libQtCoreVBox.so.4: symbol g_main_context_push_thread_default: referenced symbol not found |
|||
| #15546 | fixed | fullscreen mini toolbar missing | ||
| Description |
Arch Linux Linux minikat 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016 x86_64 GNU/Linux Using openbox 3.6.1-3 with Arch linux packages virtualbox-guest-iso-5.0.22-1-any.pkg.tar.xz virtualbox-5.0.22-1-x86_64.pkg.tar.xz virtualbox-host-dkms-5.0.22-1-x86_64.pkg.tar.xz virtualbox-ext-oracle-5.0.22-1-any.pkg.tar.xz the mini toolbar does not show properly in fullscreen. At VM start a flash is seen, but it immediately disappears and cannot be seen or raised. When using xfce4 the mini toolbar is seen with 5.0.22-1 so I believe this is an interaction between this version of virtualbox and openbox. This does not occur using the older packages virtualbox-guest-iso-5.0.20-1-any.pkg.tar.xz virtualbox-5.0.20-1-x86_64.pkg.tar.xz If of any use I have some xwininfo outputs of comparable cases in 5.0.20 & 5.0.22. virtualbox-host-dkms-5.0.20-1-x86_64.pkg.tar.xz virtualbox-ext-oracle-5.0.20-1-any.pkg.tar.xz |
|||
| #15544 | obsolete | error 0x80240031 when upgrading Windows 10 insider build on a Linux host, Virtualbox 5.0.22 | ||
| Description |
I have 2 Windows 10 virtual machine builds running VirtualBox 5.0.22 that are nearly identical except for host names, network cards and IP addresses. One runs on a Mac host, and works fine when updating to a new Windows 10 insider build (version 14367 tried most recently), and the other runs on a Linux RedHat 6.3 enterprise host, but the Linux host consistently fails the upgrade with a 0x80240031 error, even after being re-cloned successfully from the Mac. Activation looks ok. I had been able to upgrade on earlier releases of VirtualBox, so it's possible that this is a bug in the Linux Virtualbox drivers, but we need someone else to test this. |
|||

