﻿ticket,summary,version,type,created,modified,_changetime,_description,_reporter
16053,Multi Monitor: Atypical configurations - mouse desync from window dragging,VirtualBox 5.0.26,defect,2016-10-10T08:54:32Z,2022-12-22T07:25:35Z,2022-12-22T07:25:35Z,"Host: Windows 10, VBox 5.0.26, 3 monitors

Guest: Windows 10, GA VBox 5.0.27r111132, 3 monitors

Steps to reproduce: In Guest Windows display settings, change monitor order into something atypical or just change order from 1-2-3 to 3-2-1. Or use something atypical like 1-3, then 2 below.

What happens ? You can move Window when dragging but there is no way to move cursor according to guest OS configuration. Basically mouse cursor movement is desynced from window movement (while dragging windows across monitors). This is wrong and a bug.

When Multi monitor is configured in atypical way, like:
{{{
1+3
 2  (below the others)
}}}

-or-

{{{
3-2-1
}}}

Expected behavior: It should behave like host, move cursor where it is allowed to. Move windows where it is allowed to.

-Technologov, 10.10.2016.",Technologov
20937,"Multi monitor operation not working as expected, regression to 5.2",VirtualBox 6.1.34,defect,2022-05-11T09:46:12Z,2022-09-29T07:28:20Z,2022-09-29T07:28:20Z,"Host: Windows 10, 64 bit
Guest: Ubuntu 22.02 64 bit, Linux Mint 64 bit,... - Linux guest additions installed from VirtualBox's image as provided by the host

Situation: in version 5.2.x one could setup a VBox with two monitors, start the VBox and switch it to fullscreen mode - immediately on both monitors. That setting was persisent, so starting the VBox later would bring it up on two monitors in fullscreen mode without any manual action.

After upgrading to VirtualBox 6.1.34, the VBox settings were changed to ""VMSVGA"" graphics controller.

In version 6.1.34 it is not possible to activate the second monitor if the VBox is already in fullscreen mode - the menu option is not shown at all.
And in window mode one has to activate the second virtual monitor by hand each time the guest was started.

If one chooses ""VBoxVGA"" graphics controller, then the VBox apppears on two monitors in fullscreen mode immediately as it did in version 5.2. But there's then a really ugly bug with wrong mouse coordinates, that makes the VBOx unusable.

I have attached a log file of the following process:
1. starting the VBox (Xubuntu 22.04)
2. logging in
3. trying to activate the second virtual monitor - that FAILED (the window pops up and disappears immediatly)
4. once again trying to activate the second virtual monitor - worked now
5. shutting down the guest

I have tried both, a VBox that was already present and used with version 5.2.44 in the past and a brand new VBox created with version 6.1.34. There's no difference.

So IMHO that's a regression in version 6.1 compared to version 5.2 - it used to work pretty fine in version 5.2.
",Feuerfloh
16547,Full screen mode only displays on 1 screen,VirtualBox 5.1.16,defect,2017-03-10T05:13:11Z,2022-08-22T13:21:46Z,2022-08-22T13:21:46Z,"I've just upgraded to 5.1.16 hoping this problem will be resolved. When running my guest in full screen, it only displays on one of my screens (Screen 2). Does not matter if I select a different screen under View -> Virtual screen 1 -> Host host screen 1/2

If I plug screen 2 out, then it works, but the moment I plug it in, it goes back to screen 2",Jaques
20732,Win7 2 screen  boot failure,VirtualBox 6.1.30,defect,2021-12-17T08:51:54Z,2021-12-17T08:51:54Z,2021-12-17T08:51:54Z,"virtual  Win7 , 2 screen,The startup failed after KB5008212 was installed.",km Senior electrician
20678,Keep opened and running each Virtual Display in each Monitor when the Guest is left to return to the Host,VirtualBox 6.1.28,defect,2021-11-19T21:28:01Z,2021-11-22T20:13:23Z,2021-11-22T20:13:23Z,"I have in some laptops installed '''VirtualBox 6.1.28 r147628 (Qt5.6.2)''' where:

* The Hosts are MacOS (El Capitan) and Windows (7 and 10)
* The Guest is '''Ubuntu Desktop 20.04''' for each Host.

The ''Guest Additions'' was installed through the '''.iso''' file. Therefore is possible:

* Share directories copy/paste between the Host and Guest
* Copy/paste between the Host and Guest

About the Display (Monitors). For each guest instance the configurations are:

{{{
Video Memory:  64MB
Monitor Count: 2
Scale Factor:  100%
Graphics Controller: VMSVGA
}}}

When Linux is the Guest, should '''VMSVGA''' be used . So I am assuming my current configuration is ok. I am able to get the 2 monitors configured, and based on extend. Furthermore was mandatory do the following:

1. In the login screen do clic in the Settings icon and not use wayland
2. Once logged go to ''Settings -> Displays -> Join Displays'' - the resolutions are based mostly according of the Host - it how reference

'''Problem''': for any '''Host''' - when the '''Guest''' is running and applied the '''Host + F''' combination - I am able to see both monitors in full screen for each one. If I want return to the Host to do anything (I must use '''Host + F''' to return) - does not matter if the Host uses one/multiple desktop(s) - practically the 90% of times the secondary virtual monitor disappears automatically - so is mandatory do the point number 2 mentioned above. - How solve this?

What I expect is that when I left the Guest through '''Host + F''' the Guest still is running '''and''' each ''Virtual Display'' still must be opened in each Monitor where was assigned since the beginning. Then, when I return to the Guest and '''Host + F''' is used then each ''Virtual Display'' gets again the full screen of the Monitor where it was assigned",manueljordan
18872,I cannot enable second monitor,VirtualBox 6.0.10,defect,2019-08-28T08:47:59Z,2020-12-03T15:09:19Z,2020-12-03T15:09:19Z,"I set 2 displays in preferences. Linux starts with one. When I right click on the screen icon in the status bar, I see the second virtual display. Unfortunately, nothing happens when I click on ""Enable"".

linux xrandr 
{{{
Screen 0: minimum 1 x 1, current 1920 x 975, maximum 8192 x 8192
Virtual1 connected primary 1920x975+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x975      60.00*+
   2560x1600     59.99  
   1920x1440     60.00  
   1856x1392     60.00  
   1792x1344     60.00  
   1920x1200     59.88  
   1600x1200     60.00  
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.81  
   1152x864      75.00  
   1280x768      59.87  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
Virtual2 disconnected (normal left inverted right x axis y axis)
Virtual3 disconnected (normal left inverted right x axis y axis)
Virtual4 disconnected (normal left inverted right x axis y axis)
Virtual5 disconnected (normal left inverted right x axis y axis)
Virtual6 disconnected (normal left inverted right x axis y axis)
Virtual7 disconnected (normal left inverted right x axis y axis)
Virtual8 disconnected (normal left inverted right x axis y axis)
}}}




linux systemctl status vboxadd.service:
{{{
● vboxadd.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.0.11/init/vboxadd; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2019-08-28 10:31:45 CEST; 10min ago
  Process: 737 ExecStart=/opt/VBoxGuestAdditions-6.0.11/init/vboxadd start (code=exited, status=0/SUCCESS)
 Main PID: 737 (code=exited, status=0/SUCCESS)
    Tasks: 2 (limit: 4915)
   Memory: 216.7M
   CGroup: /system.slice/vboxadd.service
           ├─1231 VBoxClient --vmsvga
           └─1232 VBoxClient --vmsvga

Aug 28 10:31:42 ubuntu vboxadd[737]: modules.  This may take a while.
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: or
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Aug 28 10:31:45 ubuntu useradd[1166]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu useradd[1167]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu vboxadd[737]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Aug 28 10:31:45 ubuntu vboxadd[737]: the system is restarted
Aug 28 10:31:45 ubuntu systemd[1]: Started vboxadd.service.
}}}",Benmaxrei
18038,Mouse Integration Bug Windows 10 April 18 Host - Pointer In Wrong Location,VirtualBox 5.2.18,defect,2018-10-08T09:10:53Z,2018-10-10T08:24:54Z,2018-10-10T08:24:54Z,"I have a VirtualBox Host running Windows 10 April 2018 Update, with a Guest VM also running Windows 10 April 2018, both configured to use the same 2 screens @ 1920x1080, both scaled to 100%.

I am running VirtualBox 5.2.18 with Guest Additions 5.2.18

Since the Guest was updated to April 2018 I have been unable to get Mouse Integration to work properly.

In Mouse Integration mode the Mouse Cursor is visible in the Guest but is showing at the wrong location. If I click bottom left corner on the Windows Start menu it correctly locates the click point and shows the Start Menu. However, as I move the Mouse around the screens the location of the Click Point drifts to the right(i.e the actual Point on the virtual screen moves progressively farther away to the right as I move across the screen, whilst the Mouse Cursor tracks as normal).

This has only started happening since the Guest OS was updated to Windows April 2018.

If I turn Mouse Integration off the Mouse Cursor and click Point behave correctly, which is usable but not ideal.",C0dif0rn1c4t10n
16702,Virtual Box in Full screen mode can't switch to other virtual desktop,VirtualBox 5.1.20,defect,2017-04-26T18:09:37Z,2017-09-22T08:19:46Z,2017-09-22T08:19:46Z,"I am running Linux Mint 18.1 x64 and noticed after upgrading VirtualBox from 5.1.18 to 5.1.20 that when I enter VBOx full screen mode running Ubuntu 16.04 Desktop with fallback installed as guest that I can't switch to other virtual screen using keyboard shortcuts. My short cut was ""Control+Alt+ArrowKeys. This used to work in 5.1.18. When I exit full screen mode and just maximize VBox window it still works. Something I noticed that when in full screen mode when I try to switch virtual screens with above keyboards shortcuts I see for split of a second ""sliding"" like it is trying to do so but then it snaps back to VirtualBox on same screen. So my setup is 3x3 virtual screen setup. So if I enter full screen mode (first row third column) and try to switch to left I see for split of a second 2nd desktop about 5% or it before it snaps back to VirtualBox. I also see Mint 3x3 preview window overlay ed over Virtual box indications all configured screens. But I can switch. I have fairly recent update but this starts happening after Virtual box upgrade. I did reinstall guest tools as well",oxoocoffee
16089,MultiMonitor: Guest mode hints do not accept negative numbers for xOrigin in setModeHint.,VirtualBox 5.0.26,defect,2016-10-20T12:20:33Z,2016-10-20T12:26:58Z,2016-10-20T12:26:58Z,"The source of the bug is in VBoxHelpers.cpp (hlpResizeRect)
it attempts to maintain monitor order on display resize by comparing the monitor rectangles after the resize and finding intersections between adjacent (according to the previous monitor order) rectangles.

The problem happens if the monitor order changes - for instance, suppose we have 2 monitors - 0 and 1. 
{{{
---------- ---------
|   0    | |   1   |
---------- ---------
}}}
Suppose monitor 0 is 1024x768 starting at 0,0 and monitor 1 is 800x600 starting at 1024,0.
Suppose we call setvideomodehint with monitor 1 being moved to -1024,0 in order to move it to the left of monitor 0. 

What will happen now is that when we look for monitors X-positive adjacent to monitor 0, we'll find monitor 1.
The current code to check whether the monitors now intersect (post potential resize) is: 
(assume iRect=0 and iNextRect=1)
{{{
int delta = paNewRects[iRect].right - paNewRects[iNextRect].left;
}}}
this will result in 1024 (right of monitor 0) - -1024 (new left of monitor 1) = 2048.
next, 
{{{
        if (delta != 0)
        {
            DDCLOG((""XP intersection right %d left %d, diff %d\n"",
                     paNewRects[iRect].right, paNewRects[iNextRect].left,
                     delta));

            paNewRects[iNextRect].left += delta;
            paNewRects[iNextRect].right += delta;
        }
}}}
since delta != 0, we will now move monitor 1 on the x axis by 2048, which will lead to monitor 1 
being in the exact same location before we tried to move it. 
(-1024 + 2048 = 1024)
and we'll end up with the original monitor layout. 


Note the processing of the mode hint event from line 1689 in the log file.
",GilB
16012,Second Monitor disappears,VirtualBox 5.1.6,defect,2016-10-02T15:59:30Z,2016-10-02T16:44:02Z,2016-10-02T16:44:02Z,"Second monitor goes black a couple times a day. Unknown trigger. Can be brought back from black screen by pressing Ctrl-F twice (in and out of fullscreen) or by going into the Windows guest resolution properties and slightly adjusting the alignment of the monitor and applying.

Black screen is still in Guest realm as meta windows key still launches guest start menu in the working 1st monitor.

Host Ubuntu 14.04
Guest Windows 7

Very similar to defect #15448 but that one has Host as Win 10, and talks about the taskbar in the host not showing the correct number of instances. In my case in fullscreen the correct number of instances are shown in the host taskbar.",msorel
7492,Need a progress indicator during Snapshot creation,VirtualBox 3.2.8,defect,2010-09-17T14:38:51Z,2016-08-12T12:39:25Z,2016-08-12T12:39:25Z,"For a large VM with 5GB RAM, I tried making a snapshot of a live VM. The snapshot did not finish before 10 minutes and I could not wait any longer, so I canceled the snapshot (breaking my VM, see separate bug report http://www.virtualbox.org/ticket/6877).

I had no way of knowing when the snapshot would finish. Maybe it would have taken another few seconds... I don't know.

A progress indicator for snapshot making would be very helpful.
",BobO
15448,Second monitor disappears,VirtualBox 5.0.20,defect,2016-05-26T14:22:32Z,2016-08-10T14:41:35Z,2016-08-10T14:41:35Z,"I believe this has been raised as a ticket before and has been closed but I still have an issue with this. I run a windows 10 pro 64-bit guest on a windows 10 Home 64-bit host. Often, at least twice in an 8 hour work day, when I minimize the second monitor it disappears from the host taskbar, leaving only the one virtualbox instance for the primary screen on the host taskbar. The second monitor is restored when I hit ctrl + F twice to take virtual box out of full screen and then put it back in full screen mode.",collusion
13970,Switch desktop defect,VirtualBox 4.3.26,defect,2015-03-20T09:46:09Z,2015-03-20T09:46:09Z,2015-03-20T09:46:09Z,"On Linux Mint Mate, I have a two-monitor linux VM, and when I boot up, it starts with just one window. The second window is launched a few second later.
If in the meantime, I change desktop (using ctrl-alt right or left, for example), the first window stays in the starting desktop, but the second one is opened in the second desktop.

Would be great if they were opened both in the same desktop.

Thank you.",malarittu
13637,Second screen not working with 4.3.20 in Yosemite,VirtualBox 4.3.20,defect,2014-11-22T19:30:21Z,2014-11-22T19:31:01Z,2014-11-22T19:31:01Z,"The second screen is black. We use dual monitors and they have worked fine for years. Even with 4.3.18 it was fine. Now, I extend to the second screen in Windows and says it did but it's black. The mouse moves over there. but nothing actually works. 
The Mac side still seems fine. I thought maybe it was just that computer so I tried a second one and it's the same way.

I'm running Yosemeite 10.10.1 and Virtualbox 4.3.20 with a Windows XP SP3 Guest. The computer is a 27"" iMac with i7 and 16GB ram the second screen is an IBM 19"" lcd through a thunderbolt port.
",BryceSteiner
7895,multimon fullscreen mode is broken in 4.x,VirtualBox 4.0.0,defect,2010-12-23T18:07:34Z,2011-07-31T11:15:48Z,2011-07-31T11:15:48Z,"Hello. Im using virtualbox 3.x without this problem at all.
I have 2 monitors running in dualview mode (so i have two separated desktops). First desktop is primary.

Virtualbox Manager GUI running on first monitor and guest VM running on second monitor.
now if i press <host>+F combination (goto fullscreen) my guest VM is switched to primary monitor! if i press <host>+F again, it will go away to second monitor.

I expect to see fullscreen mode on second monitor (that is working flawless in 3.x builds)
",ddn
6815,Dual Monitors in full screen doesn't focus when dropping windows into other screen,VirtualBox 3.2.0,defect,2010-05-26T14:24:41Z,2010-05-26T14:24:41Z,2010-05-26T14:24:41Z,"When in Full Screen mode and Guest OS having 2 Virtual Monitors, moving 1 window to another screen requires an additional click to have the focus on what should already have a focus (i.e. to drag the window back to the other monitor, I'd need another click to focus the ""window/screen/monitor"" then I can click+drag. For completeness, I think this is a ""minor"" fault.  Fixing this will make it as seamless as a real dual monitor setup!",danf84
