Custom Query (16363 matches)
Results (133 - 135 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21095 | fixed | File Manager operations fail due to wrong guest path separator | ||
| Description |
When Guest Additions are installed and a file transfer is attempted through the File Manager utility, the final path separator before the file name is not handled correctly. In my case, it always ends up in the host's style. I've confirmed this bug on several different Windows host PCs with various Linux guests, but it may affect other combinations as well. I forget which release first introduced this bug, but it's been around for the last 2-3 stable releases at least. Example (Windows host with Linux guest): File "example.txt" transferred to "/home/user/Desktop" should end up at "/home/user/Desktop/example.txt". Instead, it ends up at "/home/user/Desktop\example.txt", which creates a file named "Desktop\example.txt" in the "/home/user" folder. Other (maybe all) File Manager functions suffer from the same path separator bug. Trying to rename the "Desktop\example.txt" file from the previous example, will instead rename "/home/user/Desktop/example.txt" (if it exists). |
|||
| #21394 | fixed | IGuestSession::DirectoryCreateTemp does not work with mode => fixed in SVN/next 7.0.x maintenance | ||
| Description |
The function have incorrect mode parameter verification. if (RT_UNLIKELY(!(aMode & ~07777)))
this check returns always true for valid modes and error is reported. |
|||
| #9532 | fixed | all incoming Ethernet multicast dropped => Fixed in SVN | ||
| Description |
Running a Solaris 10 guest in 4.1.2 on Solaris 11 (build 172). I have the network configured in bridged mode with the Intel Pro/1000 MT Desktop adapter (I have tried all other adapters and all exhibit this same problem). It appears that Virtualbox is dropping all incoming multicast packets. The host VNIC used by Virtualbox sends them up, but they're being dropped somewhere between the VNIC and the guest adapter (snoop in the guest doesn't show them). This is easily demonstrated by pinging 224.0.0.1 and observing that all nodes in the IPv4 subnet receive the multicast ICMP echo except for the Virtualbox guest. As a side-effect of this, IPv6 in the guest doesn't work _at all_. IPv6 depends on multicast to do neighbor discovery, router discovery, and stateless address autoconfiguration. None of this works in the guest as a result of this bug. |
|||

