VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1141 - 1143 of 16363)

Ticket Resolution Summary Owner Reporter
#18324 fixed Vbox guest additions: missing shared library dependency -> fixed in 6.0.10 Daniele
Description

Enabling 3D on host, KDE on the guest fails to start with this error:

/usr/bin/kdeinit5: symbol lookup error: /usr/lib/x86_64-linux-gnu/VBoxOGLcrutil.so: undefined symbol: crypt_r

VBoxOGLcrutil.so shared library dependencies are:

ldd /usr/lib/x86_64-linux-gnu/VBoxOGLcrutil.so

linux-vdso.so.1 (0x00007ffcbb941000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fcda8657000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fcda844f000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fcda80b1000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fcda7ead000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcda7abc000) /lib64/ld-linux-x86-64.so.2 (0x00007fcda8b53000)

Instructing linker to pre load libcrypt.so.1 fixes the issue, so I think such a dependency is missing at VBoxOGLcrutil compile time so build script needs to be fixed.

This is a regression in 6.0.2 guest additions, was working on the same guest with 5.2.24 guest additions.

#18319 fixed Serial ports (uart) don't work after upgrading from 5.2.22 to 6.0.0 and 6.0.2 -> fixed in SVN/next maintenance Vonkaz
Description

Serial ports (uart) don't work after upgrading from 5.2.22 to 6.0.0 and 6.0.2.

Host: Win10 Pro x64 1809 17763.253, COM1 native on motherboard COM2 and COM3 - using FTDI adapter.

Guest: Win10 Pro x86 1809 17763.253

Virtual Box 5.2.22 works correctly.

Virtual Box 6.0.0 does not work correctly. Opening a connection to serial ports from guest works very very slowy. After a few seconds, "VirtualBox interface" crashes with memmory violation and system automatic closes the "VirtualBox interface" background process.

Serial ports doesn't work at all on VB 6.0.2.

#18318 duplicate Virtualbox leaves multiple services running after shutdown Fochi
Description

Bug description and How to reproduce: Linux creates 3 processes when you launch VirtualBox 6.x GUI: VBoxSVC, VBoxXPCOMIPCD and the VirtualBox application.

If you close the VirtualBox application, the process should end (as it occurs with VirtualBox 5.2 and older), but the VirtualBox 6.x process stays running in the background.

Every time you launch the VirtualBox application, a new VirtualBox process is created. All those processes stay running in background after you close each application.

When you reboot your desktop, VirtualBox will automatically launch as many copies of the VirtualBox GUI as you have opened and closed in your last desktop section. And as all of them will be opened again, every passing day you have to close more and more VirtualBox instances.

Affected versions: This bug was introduced in VirtualBox 6.0.0 Host : Linux Fedora 29 last update on 2019/01/16 Desktop: KDE5 Guests : There is no need to launch a Guest machine to see this bug.

I reverted to VirtualBox 5.2 and confirmed that the bug only exists in version 6.0.0 and above.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy