View Issue Details

IDProjectCategoryView StatusLast Update
0015570CentOS-7kernelpublic2019-01-18 17:54
Status assignedResolutionopen 
Product Version7.6.1810 
Target VersionFixed in Version 
Summary0015570: CentOS 7.6.1810 running on a VirtualBox guest with a GUI has a mouse problem
DescriptionThe mouse problem was first reported for RHEL 7.6 in the following virtualbox forum post:
"Mouse only usable within single application after mouse click on RHEL 7.6"

and later in the RHEL discussion session:
"Mouse only usable within single application after mouse click on RHEL 7.6 as a VirtualBox guest"

Turns out the issue is related to the kernel version. Only the 7.6 kernels (3.10.0-957.x.el7) seem to be affected. With earlier versions or newer kernels (tested with ELRepo's kernel-lt and kernel-ml), mouse works fine.
Additional InformationThere was a useful piece of information in the referenced threads. That is, Fedora had the same problem and it went away with the kernel update to 4.17.4. So, one (or more) of the patches in that kernel update must have fixed the issue.
TagsNo tags attached.




2018-12-12 05:57

manager   ~0033318

Last edited: 2019-01-01 18:48

View 3 revisions

The first candidate is this patch:
Input: psmouse - fix button reporting for basic protocols
commit 03ae3a9caf4a59edd32b65c89c375a98ce3ea1ef

"The commit ba667650c568 ("Input: psmouse - clean up code") was pretty brain-dead and broke extra buttons reporting for variety of PS/2 mice: Genius, Thinkmouse and Intellimouse Explorer. We need to actually inspect the data coming from the device when reporting events."

A centosplus kernel has been built with the patch ( and is available from:

[EDIT] An updated version of the plus kernel is in



2018-12-12 13:57

reporter   ~0033321

Tested the centosplus kernel linked above, and it seems to resolve the issue for me. Is there an upstream RH bugzilla number that corresponds to this?


2018-12-12 14:17

manager   ~0033322

Glad to hear the positive result. Yes, I am planning to file a RHBZ as soon as I gather enough evidence that I've got the right patch. Will do so soon.


2018-12-12 16:18

manager   ~0033323

Submitted: (marked private)


2018-12-15 18:51

manager   ~0033359

The patch has been confirmed to fix the issue by multiple users.

Sidetrack: There was a problem with building the kernel module, vboxguest, when the plus kernel was installed. In VirtuslBox's Makefile for vboxvideo, RHEL 7 kernels were picked up by looking for "el7.x86_64" in the name. The original plus kernel was named "" . As a result, this kernel was not recognized as a "RHEL 7 kernel". So I built the same kernel using "" as the package name. Now Makefile sees this as a RHEL kernel and builds the vboxvideo module just fine.


2018-12-18 22:39

manager   ~0033384

Some progress made in the RHBZ:

Priority: unspecified → urgent
Severity: medium → high


2019-01-12 19:53

reporter   ~0033569

Hi there your patch appears to have fixed the issue for me (everytime I opened a new browser tab in FF or Chrome I could interact within the application but I couldn't access the Applications or Places menus). The issue only appeared once I'd installed Guest Additions (Windows 10 host running CentOS 7 in VirtualBox 6.

I'm a complete novice when it comes to this sort of thing though (I don't even really know what a kernel is), but I'm presuming at some point I won't have to boot from that kernel anymore, so what I want to know is when I don't need to use it anymore? Also what happens if I do a sudo yum update now will it pick up the latest kernel and drop this one?

Any explanation/advice would be much appreciated (but tell it to me like I'm 5!)

Thanks in advance


2019-01-13 06:38

manager   ~0033571


I'm hoping that the next kernel update will have the patch. If so, you can just go ahead and update the kernel and boot to it. If not, you'd need to keep using the plus kernel.


2019-01-13 06:55

manager   ~0033572

Last edited: 2019-01-18 17:54

View 2 revisions


There are ways to work around the issue. You can try one of the following:

(1) Log out of the GUI and log back in.
(2) Ctrl-Alt-F2 (switches to a secondary screen) and then Ctrl-Alt-F1 (switches back).
(3) On the host, change PS/2 mouse to USB Tablet.

[EDIT] (1) and (2) were confirmed to work by multiple users.

Issue History

Date Modified Username Field Change
2018-12-12 05:41 toracat New Issue
2018-12-12 05:42 toracat Status new => assigned
2018-12-12 05:57 toracat Note Added: 0033318
2018-12-12 06:10 toracat Note Edited: 0033318 View Revisions
2018-12-12 13:57 gbailey Note Added: 0033321
2018-12-12 14:17 toracat Note Added: 0033322
2018-12-12 16:18 toracat Note Added: 0033323
2018-12-15 18:51 toracat Note Added: 0033359
2018-12-18 22:39 toracat Note Added: 0033384
2019-01-01 18:48 toracat Note Edited: 0033318 View Revisions
2019-01-12 19:53 sparadox Note Added: 0033569
2019-01-13 06:38 toracat Note Added: 0033571
2019-01-13 06:55 toracat Note Added: 0033572
2019-01-18 17:54 toracat Note Edited: 0033572 View Revisions