Xorg crash when using mouse

[Ville Haapala]

Sometimes when moving mouse Xorg crashes.

I have a Logitech mouse with free spinning scroll wheel (MX Master). 100% sure way to reproduce the problem is put the wheel is free spin mode and scroll as fast as possible for a few seconds.

Also the crash happens randomly every couple of days during normal use when moving mouse normally.

I have tried both Nouveau and Nvidia proprietary GPU drivers. Same behavior on both.

Description: Ubuntu 18.04 LTS
Release: 18.04

xserver-xorg-core:
  Installed: 2:1.19.6-1ubuntu4
  Candidate: 2:1.19.6-1ubuntu4
  Version table:
 *** 2:1.19.6-1ubuntu4 500
        500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
Date: Fri Jun 22 16:09:44 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
InstallationDate: Installed on 2018-06-05 (16 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Intel Corporation S2600CW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=09005743-f23a-4610-8ea7-102ba625db6a ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2018
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C610.86B.01.01.0024.021320181901
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600CW
dmi.board.vendor: Intel Corporation
dmi.board.version: H12881-251
dmi.chassis.asset.tag: ....................
dmi.chassis.type: 17
dmi.chassis.vendor: ..............................
dmi.chassis.version: ..................
dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0024.021320181901:bd02/13/2018:svnIntelCorporation:pnS2600CW:pvr....................:rvnIntelCorporation:rnS2600CW:rvrH12881-251:cvn..............................:ct17:cvr..................:
dmi.product.family: Family
dmi.product.name: S2600CW
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

[Ville Haapala (vhaapala)]

Seems that sometimes pScreen pointer in miPointerSetPosition() is null.

In the attached crash report, the crash is happening here:
current_x = MIPOINTER(pDev)->x - pScreen->x;

#0 0x000056353930d2af in miPointerSetPosition (pDev=pDev@entry=0x56353a9d0960, mode=mode@entry=0, screenx=screenx@entry=0x7f4a11cd25c0, screeny=screeny@entry=0x7f4a11cd25c8, nevents=nevents@entry=0x7f4a11cd25bc,
    events=events@entry=0x7f4a20145050) at ../../../../mi/mipointer.c:629

(gdb) x pScreen
0x56353a660470: 0x00000000

But I have seen it also happening a few lines earlier here:
switch_screen = !point_on_screen(pScreen, x, y);

I don't know how it is possible to get the crash on line 629.
The pScreen pointer is accessed before that, and I would expect the crash already there.

And I have absolutely no idea why I'm seeing that null pointer anyway.

[Daniel van Vugt (vanvugt)]

Please report crash files by running:

  ubuntu-bug YOURFILE.crash

and then tell us the ID of the new bug created.

Although I suspect we will find this is a duplicate of bug 1771151.

[Ville Haapala (vhaapala)]

Thanks for your reply. The linked bug indeed looks similar.

ubuntu-bug does not work for me. I get graphical "Sorry, Ubuntu 18.04 has experienced an internal error." dialog, but after pressing Continue, it just closes with return code 1.

vhaapala:~✔$ ubuntu-bug _usr_lib_xorg_Xorg.0.crash
vhaapala:~✘$ echo $status
1

Probably issue with corporate proxy/firewall?

Is there any alternative way?

[Ville Haapala (vhaapala)]

I tried ubuntu-bug also at home on clean new kubuntu VM. I see same behaviour, GUI window opens, but clicking Continue just closes the window with error code 1. An I doing something wrong?

[Ville Haapala (vhaapala)]

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1778572

[Ville Haapala (vhaapala)]

Are you waiting something from me?

[Ville Haapala (vhaapala)]

Probably related:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1769397

Disabled Easystroke and so far not seeing crashes.

[Launchpad Janitor (janitor)]

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

[Daniel van Vugt (vanvugt)]

Yes your bug 1769397 was a duplicate of bug 1771151. Let's track the problem there.

[flo schneider (0penartist)]

It seems like easystroke on ubuntu is still built from 0.6.0 release and not from master.

possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190

As master is also outdated, you will need to add at least this patch:
https://github.com/thjaeger/easystroke/pull/6

"This fixes a serious bug that can lead to system instability. Without this patch, if a 'Command' action is commonly used, it will lead to so many zombie processes that the OS will be unable to launch additional processes."