Kernel 4.20: Mouse pointer dissapears near top of screen

Bug #1810586 reported by Cannot Remember on 2019-01-05

This bug report will be marked for expiration in 44 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After upgrading kernel from 4.19.9 to 4.20 my mouse pointer / cursor disappears when I move it near the top of the screen, upper most 1-3 pixels I guess. Is this a bug or feature? How to disable?

System: Host: tnb-desktop Kernel: 4.20.0-042000-generic x86_64 bits: 64 Desktop: KDE Plasma 5.12.7
           Distro: Ubuntu 18.04.1 LTS
Machine: Device: desktop Mobo: ASUSTeK model: PRIME A320M-A v: Rev X.0x serial: N/A
           UEFI: American Megatrends v: 4023 date: 08/20/2018
Battery hidpp__0: charge: 90% condition: NA/NA Wh
CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) cache: 2048 KB
           clock speeds: max: 3600 MHz 1: 1441 MHz 2: 1417 MHz 3: 1418 MHz 4: 1533 MHz 5: 1418 MHz 6: 1418 MHz
           7: 1580 MHz 8: 1486 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
           Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0, 4.20.0-042000-generic, LLVM 7.0.0) version: 4.5 Mesa 18.2.2
Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.20.0-042000-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 4250.8GB (1.7% used)
           ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_250GB size: 250.1GB
           ID-2: /dev/sda model: HGST_HMS5C4040BL size: 4000.8GB
Partition: ID-1: / size: 228G used: 67G (31%) fs: ext4 dev: /dev/nvme0n1p2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: N/A mobo: N/A gpu: 30.0
           Fan Speeds (in rpm): cpu: 0
Info: Processes: 243 Uptime: 39 min Memory: 1382.6/6960.8MB Client: Shell (bash) inxi: 2.3.56

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1810586

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Kai-Heng Feng (kaihengfeng) wrote :

Just do a kernel bisection:

$ sudo apt build-dep linux
$ git clone git://
$ cd linux
$ git bisect start
$ git bisect good v4.19
$ git bisect bad v4.20
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers