VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2248 - 2250 of 16363)

Ticket Resolution Summary Owner Reporter
#2302 fixed keys dead when remapped by xkb -> fixed in SVN Clemens Fruhwirth
Description

Xorg supports remapping keys via xkb. A typical way would be:

                Option            "CoreKeyboard"
                Option            "XkbRules"      "xorg"
                Option            "XkbModel"      "pc105"
                Option            "XkbLayout"    "us"
                Option            "XkbOptions"  "therp:desktop"

Additionally we put the following line into /etc/X11/xkb/rules/base (or xorg in the same dir):

therp:desktop         =       +therp(desktop)

This teaches Xorg to treat the option string "therp:desktop" namely by resolving it to +therp(desktop).

Further we need to add the line

--p----- -m------ therp(desktop)

to /etc/X11/xkb/symbols.dir

And finally add a file called therp to /etc/X11/xkb/symbols with the following content:

partial modifier_keys 
xkb_symbols "desktop" {
    key <AD11>  {  symbols[Group1]= [ parenleft, braceleft ] };
    key <AD12>  {  symbols[Group1]= [ parenright, braceright ] };
    key <AE09> { symbols[Group1]= [         9,    bracketleft       ]       };
    key <AE10> { symbols[Group1]= [         0,    bracketright      ]       };
};

The effect of these lines is that the keys () and [] are swapped on the keyboard. I personally like that as I type round brackets more often and I like them to be accessible without the Shift modifier key.

However, as soon as a key is touched by xkb, it goes dead for VirtualBox. Notice that 0 and 9 wasn't changed, however 0 and 9 don't work even unshifted.

To make it work I have to adjust the layouts manually in the vbox source code and supply vbox with a keymap that resembles my remappings precisely.

#2303 worksforme WinXP install: Error 2867 Mike Duskis
Description

While installing VirtualBox 2.0.2 (VirtualBox-2.0.2-36488-Win_x86.msi) on a WinXP SP2 machine, a The system cannot open the device or file specified dialog popped up. The msi log shows

MSI (s) (98:CC) [09:47:06:888]: Note: 1: 1309 2: 5 3: D:\installers\VirtualBox-2.0.2-36488-Win_x86.msi 
DEBUG: Error 2867:  The error dialog property is not set
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2867. The arguments are: , , 
MSI (c) (B8:94) [09:47:06:888]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

The system cannot open the device or file specified.
MSI (s) (98:CC) [09:47:08:151]: MainEngineThread is returning 110

I had VirtualBox 2.0.2 up and running on this machine until our IT department re-imaged the drive.

#2304 invalid nat socks connector Imre Péntek
Description

If I figure out correctly the virtual network device "NAT" interprets individual outgoing packages and compiles them into a new TCP connection initiated by the physical machine. So it would be possible to attach a socks proxy for the nearer endpoint of the TCP connections. Also it would be useful for me.

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