I'm using ArchLinux (guest) inside a VirtualBox machine (windows 10 host).
The mouse always worked until now.
The symptoms:
On Chromium, the click (left/right) on the extensions, on the address bar, on the tabs, on the bookmarks doesn't work (it does nothing, it's like I'm not clicking). Sometimes, clicks altogether doesn't work at all anywhere (not even on the page or anything).
On xterm, when I Ctrl+Click to open the config menu, it works. But when I hover and/or click into the menu, it does nothing (the highlight when hovering doesn't show either).
Globally, sometimes the mouse does not work at all, I can only move it (not click)
I'm using i3 (with Xorg)
$ i3 --version
i3 version 4.15 (2018-03-10)
$ VBoxClient --version
5.2.12r122571
$ pacman -Q | grep virtualbox
virtualbox-guest-modules-arch 5.2.12-10
virtualbox-guest-utils 5.2.12-2
I did a system upgrade recently, that might installed something that cause the issue.
Please tell me what you need (logs, version, ...), I really need to fix this really weird problem!
EDIT: It works fine if I disable the Mouse Integration but the cursor is a bit laggy. So it seems that the problem is coming from VirtualBox.
UPDATE: I've try to install a fresh Manjaro VM and the mouse does not work properly either. And also, sometimes the mouse works perfectly fine.
UPDATE: I've tested with evtest, xinput and xev. So, I basically have 3 main devices detected:
VirtualBox USB Tablet
VirtualBox mouse integration
ImExPS/2 Generic Explorer Mouse
Here is what each devices registers with which tool:
-- evtest
Device | Registers clicks | Registers position |
=========================================================================
VirtualBox USB Tablet | no | no |
VirtualBox Mouse Integration | no | yes |
ImExPS/2 Generic Explorer Mouse | yes | no |
-- xinput test
Device | Registers clicks | Registers position |
=========================================================================
VirtualBox USB Tablet | no | no |
VirtualBox Mouse Integration | no | yes |
ImExPS/2 Generic Explorer Mouse | sometimes | no |
-- xev
Registers only mouse movement consistently, clicks are sometimes registers
When I say "sometimes", it means like in a boot session; what happens is that every time I start my VM everything "works" (the clicks and movement are registered by each test program listed above, but the symptoms are still present). If the VM stays up for too long, the clicks are not registered anymore by the programs, and don't work anymore anywhere.
Hope everything is understandable.
Thanks.
I also had this issue.
Looks like a more general (not Arch Linux specific) issue with VirtualBox and 4.17 Linux kernels and has a bug ticket here: https://www.virtualbox.org/ticket/17827
My personal workaround until a solution is available is to force that the vboxguest kernel module is not loaded by adding a file modprobe.conf to /etc/modprobe.d with content
install vboxguest /bin/false
(I assume you can alternatively blacklist both vboxguest and vboxsf or uninstall virtualbox-guest-utils)
Unfortunatly, this loses all Virtual Box Guest Addition functionality, such as clipboard sharing.
Edit: Another workaround mentioned in the ticket also works for me:
after boot, start i3 once and then exit it again immediately ($mod+shift+E or, if the confirmation is not usable without mouse: pkill i3).
Start i3 again (startx) and the mouse seems to work fine.
I had the same or even worse problems with the mouse.
Host: ArchLinux
Guest: Archlinux + i3w (+KDE Plasma)
Disabling the window manager SDDM
systemctl disable sddm
added as a default for the KDE Plasma and starting i3w with
xstart
after setting
exec i3
in
~/.xinitrc
seems to have fixed the problems.
It seems that i3w collides with the default window manager.
Related
I'm trying to install Elementary OS in VirtualBox, but the minimum resolution of the OS is 1024x768 and VirtualBox always boots in a much lower resolution. I can't install Guest Additions until the OS has been fully installed and I am on the desktop. I can't go through with the installation, though, because I only see about 60% of the screen in the top left corner. I've tried increasing video resolution to 128mb, but as I thought, that didn't work. Is there a way to increase the resolution with Guest Additions or something else before booting the system to install it?
I had an issue with the installation of Elementary OS 6 with VirtualBox for the same reason. The right side and bottom portion of the installer screens were cutoff. That area of the screen has buttons for back, submit, cancel.
I resolved this by making to selection to erase/complete install, then using the tab key twice followed by the enter key. Apparently this sequence of keystrokes allowed me to initiate the full installation script successfully.
same issue here,
end up add boot kernel parameter to fix this,
when first boot prompt(5 secs),
hit any key within the 5 secs count down to show boot options,
hit TAB to edit first option,
add the vga=ask to the end of boot kernel lines.
then it will show another 30 secs count down for VGA mode selection,
hit ENTER to choose proper one, in my case I choose 1280x800x32.
that's all,
more detail regarding boot vga parameters can refer to this URL.
https://linuxhint.com/set_screen_resolution_linux_kernel_boot/
Im trying very hard to like virtualbox, but so far I find it so much worse than vmplayer in so many ways. If it wouldnt take me hours to install everything back into vmplayer i would have moved back days ago
When I open my ubuntu vm my host OS's (windows 10) toolbar is still visible at the bottom of the screen, cutting off the actual virtualbox toolbar
Please help me
(edit) It is in fullscreen mode already, it just still shows the toolbar/taskbar from the host OS
Open Task Manager of Windows 10, Select "Windows Explorer" and Restart.
Reference Link
I had this same issue. The Windows 10 taskbar was still showing when I had VirtualBox in fullscreen mode, and what caused it for me was I had a program called Rufus (for creating bootable USBs) open and it was keeping the taskbar from hiding. Once I closed Rufus, everything worked as it should. So, maybe you had a program keeping focus on the taskbar, something that needed attention, and wouldn't let the taskbar hide.
I ran into the problem once. Not sure what had caused the that but I managed to find a solution by enabling "task bar" hiding option in host windows 10 machine.
Right Click on Task Bar -> Task Bar Setting -> Enable Task Bar hiding Option.
You are able to switch to fullscreen mode on the VM, this should hide the Host OS.
This image shows you where you can find the option:
If this is not what you are looking for, please elaborate on your problem, maybe add a screenshot showing the problem you are having.
I just experienced this exact problem, namely Windows 10 host taskbar would not go away despite the guest being in full screen. Even though this question is old, since this question got the top google page rank, I thought I would share how I fixed it.
I fixed it by shutting down Virtualbox and then rebooting the Windows 10 host. It is possible as others have pointed out that some app was keeping the taskbar active, but I couldn't find any such app. If it was some rogue app that was just running as a process (with no taskbar presence), the reboot nuked it from orbit and fixed the problem.
After installation virtualbox tools You can press
host + F (in my case Ctrl + F)
buttons to run fullscreen in virtualbox.
I'm trying to make a Win 7 64 bit guest machine. When it's time to load the ISO, I try to load it and I get the following error
The VM session was aborted.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
What's a fix for this? Thank you.
I have the same issue, and hopefully there will be a bug-fix for it soon.
In the meantime, I have managed to start the install process (in my case for Linux mint 17.2 rather than windows) by attaching the .iso image in the VirtualBox IDE Storage Settings page rather than the "mount" dialog that causes the error.
Open the settings for your VM in the VirtualBox UI, go to Storage, click on the "empty" entry in the list of IDE Controllers, and select the disk icon over to the right of the screen. Finally, select to "Choose Virtual Optical Disk File", and select your .iso of choice. Then start the VM and it should boot just fine.
I hope it helps for your case too!
update the extension pack was my solution
Maybe it will help.
I turned off sound card , and at virtual machine I had "audio" controller turned on.
When I turned off audio controler virtual machine start normaly.
BR Simon
Backed up the last saved snapshot from C:\Users\\VirtualBox VMs\Ubuntu\Snapshots
Go to Machine> Ignore last saved state.
Restart VM.
This worked.
This issue most likely happened for me because my Windows 10 randomly restarted a couple of time, with BSOD.
Error code
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
Menu -> Machine -> Reset all warnings
worked for me
Menu -> Machine -> Discard Saved State...
This worked.
start your virtual machine
start ubuntu
open settings in ubuntu and go to display
set resolution to 16:9
and you are done
I am trying to add touchpad gesture support to an existing MFC application. I'm using VS 2010, with the new MFC which supports OnGestureZoom and OnGesturePan(), however, I can't make these work. I have breakpoints in them, but they are never called.
I have a touchpad on my laptop, and it is working with the default windows processing (i.e. zoom comes through as a mouse scroll wheel event). However, I want to override this zoom behaviour and also process panning, rotation, etc.
In OnCreate(), I am calling
int lval = GetSystemMetrics(SM_DIGITIZER);
int ltouches = GetSystemMetrics(SM_MAXIMUMTOUCHES);
and both functions return zero, so this indicates that there is some other problem here that is stopping gestures from working correctly
I have also tried calling RegisterTouchWindow() in OnCreate, but this makes no difference.
Edit to add - I've tried following this simple tutorial [http://msdn.microsoft.com/en-us/windows7trainingcourse_win7multitouchgesturemfc_topic2.aspx][1], but still no joy. At Task 2, step 4, my application simply says that "No touch input is currently available."
What O/S are you running on?
Also check if the Tablet PC Input service is started -- the GetSystemMetrics function for SM_DIGITIZER says "Nonzero if the current operating system is Windows 7 or Windows Server 2008 R2 and the Tablet PC Input service is started".
I'm wondering how to programmatically change to one of the available terminals from an embedded Qt application.
The application is invoked via application -qws. Graphically it is configured with the Linux framebuffer (support compiled into the kernel) with the tty drivers enabled.
The reason for doing this programmatically is that Ctrl+Alt+FX does not work to switch ttys.
Firstly, I tried the obvious cheating mechanism - overriding keyPressEvent I added system("chvt 2"); Unfortunately, this did not work.
Instead, I looked directly at the source of chvt.c in busybox. Essentially, that boiled down to doing:
fd = open("/dev/console", O_RDRW);
ioctl(fd, VT_ACTIVATE, vt_num);
ioctl(fd, VT_WAITACTIVE, vt_num);
Ignoring the use of xioctl and detecting the correct tty - I know /dev/console exists and I can get a RW file handle on it.
Again, no luck.
So taking my cue from chvt.c I decided to iterate over all the framebuffer devices present until I found one that was receiving keyboard input; then I ran
fd = open("/dev/fb1", O_RDRW);
ioctl(fd, VT_ACTIVATE, vt_num);
ioctl(fd, VT_WAITACTIVE, vt_num);
That caused a black screen as per any normal tty change, except that the framebuffer device returned afterwards, bringing my app back with it.
So - my question - without exiting my application, I'd like to be able to programmatically switch to a tty of my choice, and then be able to switch back using the usual ctrl+alt+fX mechanism.
Environment:
Qt 4.7.4
Linux 3.3.3
Buildroot 2011.11
Busybox 1.19
uClibc 2.21
I suspect, but am not certain, that the cause of ctrl+alt+fX not working in the first place may be the cause of the tty change not working programmatically as per chvt.
I should point out at this stage that, confusingly, the zap keys (ctrl+alt+backspace) do work as expected.