I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock,
rebooted and then reproduced the issue. Luckily I've found one way to
reproduce this, albeit somewhat convoluted and still a bit unreliable,
involving Synaptic and window tiling. And as it doesn't seem to trigger
the issue when using another account, I'm now working through settings
differences between the two in hopes of finding something crucial.
While doing so, I did discover that dconf-editor is similarly affected:
touko 12 16:09:32 saegusa gnome-shell[8208]: WL: compositor bug: The
compositor tried to use an object from one client in a 'wl_pointer.enter' for a
different client.
touko 12 16:09:32 saegusa gnome-shell[8208]: WL: error in client
communication (pid 12364)
touko 12 16:09:32 saegusa dconf-editor[12364]: Error reading events from
display: Katkennut putki
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: compositor bug: The
compositor tried to use an object from one client in a 'wl_pointer.enter' for a
different client.
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: error in client
communication (pid 12796)
touko 12 16:09:34 saegusa gnome-terminal-[12796]: Error reading events from
display: Katkennut putki
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service:
Main process exited, code=exited, status=1/FAILURE
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service:
Failed with result 'exit-code'.
touko 12 16:09:34 saegusa systemd[3569]:
vte-spawn-da1941e8-60e5-48e5-868b-7348dd1158c7.scope: Succeeded.
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to
desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to
desktop: this.layout.get_child_at(...) is null
Looks like dconf-editor did not exit with FAILURE, but the dconf-editor
window did disappear just as Gnome terminal's did.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1877568
Title:
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)
Status in gnome-terminal package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Status in wayland package in Ubuntu:
Incomplete
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-[11639]: Error reading events
from display: Katkennut putki
touko 08 11:35:16 saegusa systemd[4153]:
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]:
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service:
Main process exited, code=exited, status=1/FAILURE
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service:
Failed with result 'exit-code'.
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.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
terminal also exhibits other misbehaviour wrt. to this, occasionally
refusing to get focus, or alternatively losing the focus, despite
mouse cursor being over the terminal window.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland 2:1.20.8-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
Uname: Linux 5.4.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 8 15:22:28 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed
(WARNING! Diff between built and installed module!)
fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed
(WARNING! Diff between built and installed module!)
xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
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-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fi_FI.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
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.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
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.5-0ubuntu2~16.04.1
xserver.video_driver: modeset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
