WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
mutter (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
wayland (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal:
touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639)
touko 08 11:35:16 saegusa gnome-terminal-
touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-
touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-
I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week.
Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland 2:1.20.8-2ubuntu2
ProcVersionSign
Uname: Linux 5.4.0-30-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CompizPlugins: [core,composite
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 8 15:22:28 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
fwts-efi-
fwts-efi-
xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2016-10-13 (1302 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: System manufacturer System Product Name
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fi_FI.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1505
dmi.board.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Tue Mar 20 15:09:56 2018
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.
xserver.
Please also follow these instructions to help us identify the crash:
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.