Custom Query (16363 matches)
Results (1336 - 1338 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17859 | duplicate | Can't copy a ".SVN" directory from VM to HOST trough directory share | ||
| Description |
Hi, When I copy a directory containing a ".svn" subdirectory which is hidden (typically a Tortoise SVN managed project) from VM to Host trough the "shared directory" feature, the copying stops at the very first file of the .SVN subdir without any error, any alert, nothing. It stops. Drag & drop or copy/paste behave identically. I have the same problem too with the (hidden too) ".vs" subdir. It seems that Virtual Box does not handle correctly directories beginning with a dot in a local share , even under Windows. Physical and Virtual machine, the two ones run W10-64. The log for this shared directory is : SharedFolders host service: Adding host mapping 00:00:04.453014 Host path 'C:\Users\xxxx\Projets', map name 'Projets', writable, automount=true, create_symlinks=false, missing=false But no error is logged. |
|||
| #17855 | fixed | [5.2.14][QT 5.11] VBoxManager doesn't store correctly values in ~/.config/VirtualBox/VirtualBox.xml | ||
| Description |
Hello. There is a bug in VBoxManager when using it with QT 5.11. I can reproduce it both on a Manjaro Linux based laptop and an Archlinux based PC. When you launch VirtualBox on a linux distribution with QT 5.11, both toolbar and statusbar are hidden. Even if you display both of them, on shutdown, it is not stored correctly. Here is a screenshot of this bug. When I looked at ~/.config/pVirtualBox/VirtualBox.xml I noticed these both entries: <ExtraDataItem name="GUI/Statusbar" value="false"/> <ExtraDataItem name="GUI/Toolbar" value="false"/> If you change both false by true with VirtualBox closed on next start, both bars are displayed. |
|||
| #17852 | invalid | [Hardenning Issues] - All proposed options tryed | ||
| Description |
Hi, I was working with vbox for a while without issues. This week I began working with a new laptop and I'm not able to start any kind of VM that worked before and I'm really stuck without being able to work. I already tried every solution described in this forum and all the guidelines. Current status: Windows 10 Pro vagrant 2.1.1 virtual box 5.2.12 already tryed:
In attachement there's the hardening log. Anyone have a hint on what could be the issue? Thanks |
|||

