VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1831 - 1833 of 16363)

Ticket Resolution Summary Owner Reporter
#16649 invalid Mobile USB Tethering stops working after reconnection -> not virtualisation related, possibly device problem Knorxi
Description

Steps to reproduce: 1) Plug in Android Device, activate tethering, share USB 2.0 and Filter Android Dev (SAMSUNG_Android FFFF) 2) Start Linux Guest (Lubuntu), surf 3) Disconnect Android USB Cable and reconnect it, activate tethering 4) Guest shows working network connection, but internet connection is lost

This worked in prev. versions of virtual box (> 5.0.20)

#16648 wontfix Linux VBox 5.1 ignores modifier key mapping (xmodmap) -> design decision, see work-arounds jamshark70
Description

In Ubuntu, I use xmodmap to make ctrl and alt easier to type.

Physical keyboard, bottom row from left: Ctrl, Super, Alt, spacebar, ...

Remapped: Super, Alt, Ctrl, spacebar

clear control
clear mod1
clear mod4
clear mod5
!!!! These are the codes for the way *I* want the keys
!!!! For some reason, if Super_L appears in mod1, it doesn't work.
!!!! Hitting Alt (originally Super) by itself *acts* like Super
!!!! So I have to rename the symbols here
keycode  64 = Control_L
keycode 108 = Control_R
keycode  37 = Super_L
keycode 105 = Super_R
keycode 133 = Alt_L
keycode 134 = Alt_R
keycode 135 = Menu
add control = Control_L Control_R
add mod1    = Alt_L Alt_R
add mod4    = Super_L Super_R

Under VirtualBox 4.8, the remapping carried through into the guest OS.

In VBox 5.1, the guest seems to be catching the keystrokes before the xkb/xmodmap layer, so the remapping is broken.

https://forums.virtualbox.org/viewtopic.php?f=7&t=64108&p=309293&hilit=xmodmap#p309293

Rationale: I have a repetitive strain injury, so it's important for me to avoid unnecessary muscle movement. Ctrl is the most commonly used modifier, but it's in the worst possible place on the keyboard -- and in fact, reaching for the Ctrl key with my pinky has been extremely stressful. I get a lot of relief from moving Ctrl to be basically under my thumb.

Now I have to retrain my muscle memory to use the physical Ctrl key, but only in a VirtualBox guest. It's very bizarre... and I can't understand why it was changed, because it used to work perfectly.

I suppose the developer perspective might be, "Well, we can't support all kinds of nonstandard configurations." But... this is an adaptation for a physical condition. Software should adapt to our needs, not the other way around.

#16647 wontfix Linux host VBox 5.1.18 ignores GTK color theme -> Qt5 issue jamshark70
Description

Ubuntu 14.04. I'm using "Dorian-theme"[1]. In just about every application, I get dark window title bars, menu bars, dialog box backgrounds etc.

When I was using VirtualBox 4.x, VBox menu bars and backgrounds were dark, matching the theme.

I recently upgraded to 5.1, and backgrounds have regressed to light color.

It's not a high priority issue, but it's jarring to have two brightly colored bars (VBox menus "File, Machine...", and the VBox status bar at the bottom) on the screen where everything else is dark.

Since VBox used to be able to handle color themes properly, and now it doesn't, technically it's a regression.

Attached is a screenshot showing Firefox menu bars (OK) vs. VBox (not OK).

[1] https://www.gnome-look.org/content/show.php/Dorian+Theme?content=157200

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