Wacom crashes Xorg

[sander]

The X Server consistently crashes when my Wacom Intuos Pro Medium tablet is attached to my Dell XPS 13 laptop whilst I have a second screen connected using the HDMI port on the Dell DA300 hub. The crash does not immediately happens when the Wacom devices is attached, but during the use of the tablet. It is easy to repeat this crash very fast by pushing the tablet buttons and using the pen. In less than 15 seconds, the X Server will crash. When the second screen is not attached to my laptop, the X Server keeps running flawlessly.

My Dell XPS 13 laptop is running the preinstalled 18.04 LTS, Gnome 3.28.2 and it has Intel UHD Graphics 620 (WHL GT2).

I tried the tabled on a desktop with 2 screens attached running Ubuntu 20.04 LTS and Gnome 3.36.3. It has Intel HD Graphics 2500 (IUB GT1). It works without issues. The bug does not arise on this device!

Please find attached gdb details (not sure if I did well; I have never used this tool before).

Any idea how to fix this? Or maybe a workaround? My Wacom tablet is almost useless on my laptop due to this bug. If I want to use it, I have to detach my second screen and work on the small laptop screen.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[sander (s-devrieze)]

As there are several crash files in that directory, I tried again to check
the date on a new crash report, but no new files were created:

-rw------- 1 whoopsie whoopsie 0 apr 26 11:47
_usr_bin_eid-viewer.1027.uploaded
-rw------- 1 whoopsie whoopsie 0 apr 22 11:24
_usr_bin_gjs-console.1027.uploaded
-rw-r----- 1 sander whoopsie 25M apr 26 17:22
_usr_bin_gnome-shell.1027.crash
-rw-rw-r-- 1 sander whoopsie 0 apr 26 17:22
_usr_bin_gnome-shell.1027.upload
-rw------- 1 whoopsie whoopsie 0 apr 26 17:22
_usr_bin_gnome-shell.1027.uploaded
-rw-r----- 1 gdm whoopsie 4,9M apr 26 16:11 _usr_bin_Xwayland.120.crash
-rw-r--r-- 1 gdm whoopsie 0 apr 26 16:11
_usr_bin_Xwayland.120.upload
-rw------- 1 whoopsie whoopsie 0 apr 26 16:13
_usr_bin_Xwayland.120.uploaded
-rw-r----- 1 root whoopsie 5,3M apr 26 16:02 _usr_lib_xorg_Xorg.0.crash
-rw-r--r-- 1 root whoopsie 0 apr 26 16:02 _usr_lib_xorg_Xorg.0.upload
-rw------- 1 whoopsie whoopsie 0 apr 26 16:13
_usr_lib_xorg_Xorg.0.uploaded
-rw-r----- 1 sander whoopsie 119M apr 23 12:58
_usr_lib_xorg_Xorg.1027.crash
-rw-r--r-- 1 sander whoopsie 0 apr 22 14:39
_usr_lib_xorg_Xorg.1027.upload
-rw------- 1 whoopsie whoopsie 0 apr 22 15:24
_usr_lib_xorg_Xorg.1027.uploaded
-rw-r----- 1 gdm whoopsie 343K apr 26 16:11
_usr_lib_xorg_Xorg.120.crash
-rw-r--r-- 1 gdm whoopsie 0 apr 26 16:11
_usr_lib_xorg_Xorg.120.upload
-rw------- 1 whoopsie whoopsie 0 apr 26 16:13
_usr_lib_xorg_Xorg.120.uploaded
-rw-r----- 1 root whoopsie 178K apr 26 15:59
_usr_share_session-migration_scripts_01_migrate_from_keyring.0.crash
-rw-r--r-- 1 root whoopsie 0 apr 26 15:59
_usr_share_session-migration_scripts_01_migrate_from_keyring.0.upload
-rw------- 1 whoopsie whoopsie 0 apr 26 15:59
_usr_share_session-migration_scripts_01_migrate_from_keyring.0.uploaded

Maybe no new report is created when there is already a crash report? Can I
safely delete all contents of that directory? Or do you know which crash ID
you need?

In my attempt to generate a new crash report, I also noticed the gdb errors
are not consistently the same. See attached. The first time the X Server
stalled for a long time and thereafter the Wacom tablet did not work well.
Using the Gimp pen tool, it drew dots instead of a line. I had to unplug
the Wacom tablet to get it working again in a normal manner....and to get
the real crash.

--
Mvg, Sander Devrieze.

Op di 27 apr. 2021 om 12:00 schreef Sebastien Bacher <
<email address hidden>>:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot,...

[sander (s-devrieze)]

Ok, I also noticed a coredump file was created in my home directory
yesterday in an attempt to enable coredumps. The attached backtrace was
generated using the instructions on
https://wiki.debian.org/XStrikeForce/XserverDebugging

--
Mvg, Sander Devrieze.

Op di 27 apr. 2021 om 13:25 schreef Sander Devrieze <
<email address hidden>>:

> As there are several crash files in that directory, I tried again to check
> the date on a new crash report, but no new files were created:
>
> -rw------- 1 whoopsie whoopsie 0 apr 26 11:47
> _usr_bin_eid-viewer.1027.uploaded
> -rw------- 1 whoopsie whoopsie 0 apr 22 11:24
> _usr_bin_gjs-console.1027.uploaded
> -rw-r----- 1 sander whoopsie 25M apr 26 17:22
> _usr_bin_gnome-shell.1027.crash
> -rw-rw-r-- 1 sander whoopsie 0 apr 26 17:22
> _usr_bin_gnome-shell.1027.upload
> -rw------- 1 whoopsie whoopsie 0 apr 26 17:22
> _usr_bin_gnome-shell.1027.uploaded
> -rw-r----- 1 gdm whoopsie 4,9M apr 26 16:11
> _usr_bin_Xwayland.120.crash
> -rw-r--r-- 1 gdm whoopsie 0 apr 26 16:11
> _usr_bin_Xwayland.120.upload
> -rw------- 1 whoopsie whoopsie 0 apr 26 16:13
> _usr_bin_Xwayland.120.uploaded
> -rw-r----- 1 root whoopsie 5,3M apr 26 16:02 _usr_lib_xorg_Xorg.0.crash
> -rw-r--r-- 1 root whoopsie 0 apr 26 16:02
> _usr_lib_xorg_Xorg.0.upload
> -rw------- 1 whoopsie whoopsie 0 apr 26 16:13
> _usr_lib_xorg_Xorg.0.uploaded
> -rw-r----- 1 sander whoopsie 119M apr 23 12:58
> _usr_lib_xorg_Xorg.1027.crash
> -rw-r--r-- 1 sander whoopsie 0 apr 22 14:39
> _usr_lib_xorg_Xorg.1027.upload
> -rw------- 1 whoopsie whoopsie 0 apr 22 15:24
> _usr_lib_xorg_Xorg.1027.uploaded
> -rw-r----- 1 gdm whoopsie 343K apr 26 16:11
> _usr_lib_xorg_Xorg.120.crash
> -rw-r--r-- 1 gdm whoopsie 0 apr 26 16:11
> _usr_lib_xorg_Xorg.120.upload
> -rw------- 1 whoopsie whoopsie 0 apr 26 16:13
> _usr_lib_xorg_Xorg.120.uploaded
> -rw-r----- 1 root whoopsie 178K apr 26 15:59
> _usr_share_session-migration_scripts_01_migrate_from_keyring.0.crash
> -rw-r--r-- 1 root whoopsie 0 apr 26 15:59
> _usr_share_session-migration_scripts_01_migrate_from_keyring.0.upload
> -rw------- 1 whoopsie whoopsie 0 apr 26 15:59
> _usr_share_session-migration_scripts_01_migrate_from_keyring.0.uploaded
>
> Maybe no new report is created when there is already a crash report? Can I
> safely delete all contents of that directory? Or do you know which crash ID
> you need?
>
> In my attempt to generate a new crash report, I also noticed the gdb
> errors are not consistently the same. See attached. The first time the X
> Server stalled for a long time and thereafter the Wacom tablet did not work
> well. Using the Gimp pen tool, it drew dots instead of a line. I had to
> unplug the Wacom tablet to get it working again in a normal manner....and
> to get the real crash.
>
> --
> Mvg, Sander Devrieze.
>
>
> Op di 27 apr. 2021 om 12:00 schreef Sebastien Bacher <
> <email address hidden>>:
>
>> Thank you for taking the time to report this bug and helping to make
>> Ubuntu better. It sounds like some part of the system has crashed. To
>> help us find the cause of the crash please follow these steps:
>>
>> 1. Loo...