VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (853 - 855 of 16363)

Ticket Resolution Summary Owner Reporter
#13238 fixed shift and ctl keys stop working after view mode switch in linux guest -> fixed in 4.2 series and later releases after 4 August 2014 zeny entropy
Description

Host Arch Linux x86_64 3.15.5-2 SMP PREEMPT (LXDE desktop) Guest Arch Linux x86 - Guest boots in full screen mode OK (2 screens). Goes to LXDE destkop OK. Switch to seamless or scaled mode, and back to full screen, then shift-key or ctrl-keys (modifiers) have no effect ie shift-a == ctrl-a == 'a' Shift to seamless again, and shift-a == 'A'. but still 'a' in full screen mode. Annoyance makes view mode switch inadvisable.

#740 fixed shift + certain keys unusable Rusty Lynch
Description

I am unable to use left shift + (tab - right bracket) and right shift + (u - backspace)

This was a bug in version in early 2006 when i first tried VBox and uninstalled it and no problems. i tried to install and same problem but now no way to uninstall, no uninstall in start menu or control panel

I am using windows media center as host on Compaq presario and this effects Host and Guest with and without VBox running.

#7198 invalid sharing guest impossible because xml settings files written in mode 600 instead of 660 jeff stern
Description

(this is with linux/ubuntu host and windowsxp guest, with vbox 3.2.6 -- not the OSE, but the linux host downloaded from http://www.virtualbox.org/wiki/Linux_Downloads for ubuntu 10.04 AMD64.)

i noticed that Virtualbox writes its .xml config files in the ~/.VirtualBox and ~/.VirtualBox/Machines/MACHINE_NAME directories in mode 600, which makes it impossible to share a virtualbox guest between users on the same system. they should be written in mode '660'.

furthermore, if i as root correct the permissions to be 660 on the 2 relevant .xml files contained in these directories, then the next time VirtualBox is run for this guest, these 2 .xml files will unfortunately have their permissions re-set to 600. :o(

this shared setup worked successfully for me using the 3.1.6 OSE version from ubuntu -- i did not have this problem with the OSE. now that i've upgraded (in an attempt to get access to my USB devices), i can't share the guest between the 2 users.

my use case:

if i have two users on my home box: usera and userb. both users belong to group 'users'. i have /home/usera/.VirtualBox and /home/userb/.VirtualBox both sym-linked to /home/virtualbox/.VirtualBox, and /home/virtualbox/.VirtualBox is group-owned by 'users' and has the setgid bit set so it is in mode 2775. thus, every file and sub-directory created under it should belong to group 'users' (and this is true). my vbox name is 'WindowsXP'.

the problem is that if usera uses the system, then, in the /home/virtualbox/.VirtualBox directory, the VirtualBox.xml file will have its permissions set to 600 when they should be 660:

-rw------- 1 usera  users     2261 2010-07-18 11:58 VirtualBox.xml

now only usera can use the system.

now if usera shuts down the guest and logs off and userb signs in and tries to access the guest, userb will get a dialogbox popping up saying:

VirtualBox - Critical Error
-------------------------------
Failed to create the VirtualBox COM object.
The application will now terminate.
Runtime error opening '/home/userb/.VirtualBox/VirtualBox.xml' for reading: -38 (Access denied.).
/home/vbox/vbox-3.2.6/src/VBox/Main/VirtualBoxImpl.cpp[535] (nsresult VirtualBox::init()).

and in the Details of that dialog box, it says:

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {3f36e024-7fed-4f20-a02c-9158a82b44e6}

(note that /home/userb/.VirtualBox/VirtualBox.xml is really /home/virtualbox/.VirtualBox/VirtualBox.xml)

now if i try to reset the file permissions on the /home/virtualbox/.VirtualBox/VirtualBox.xml file:

$ chmod 660 /home/virtualbox/.VirtualBox/VirtualBox.xml

it makes that error go away, but now userb will get another, similar message, about the /home/userb/.VirtualBox/Machines/WindowsXP/WindowsXP.xml file (which of course is really /home/virtualbox/.VirtualBox/Machines/WindowsXP/WindowsXP.xml).

so i reset that 2nd XML file to mode 660 as well:

$ chmod 660 /home/virtualbox/.VirtualBox/Machines/WindowsXP/WindowsXP.xml

so that that file (which also belongs to 'users' group already) is accessible, now userb can fire up the WindowsXP guest. (assuming of course, that usera has shut down the guest from their side first).

however, now the reverse is true: after userb has used the guest, VirtualBox has rewritten those files and reset their mode to 600 so that they are not accessible by the group, only owner. so now usera cannot use the system. these files should be preserved in mode 660.

please let me know if there is a simple config to override this, or if i'm missing something super-obvious (most usually am :-) ) or if you need any more information, and thanks.

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