Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Affected version
- Ubuntu 19.10
- Gnome Shell 3.34.1+git20191024-1ubuntu1~19.10.1
- X11
Bug summary
Gnome-Shell freezes when I attempt to resize the Style window of LibreOffice.
100% reproductible
Steps to reproduce
- Open Libreoffice
- attempt to resize the style window
- Gnome-Shell is frozen for a few seconds
What happened
Gnome-Shell froze.
What did you expect to happen
It should have worked
Relevant logs, screenshots, screencasts etc.
Looking at journalctl
, some interesting info:
gnome-shell[2668]: Could not create selection source for X11: Le format TARGETS n'est pas pris en charge
gnome-shell[2668]: Object .Gjs_WindowSwitcherPopup (0x55dc00da4780), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[2668]: == Stack trace for context 0x55dbe9e5e350 ==
gnome-shell[2668]: #0 55dbf2faf4e0 i resource:///org/gnome/shell/ui/windowManager.js:2097 (7f04b0d3e8b0 @ 410)
gnome-shell[2668]: #1 55dbf2faf420 i self-hosted:981 (7f04b0c34160 @ 474)
gnome-shell[2668]: clutter_actor_destroy: assertion 'CLUTTER_IS_ACTOR (self)' failed
gnome-shell[2668]: Could not create selection source for X11: Le format TARGETS n'est pas pris en charge
gnome-shell[2668]: Object .Gjs_WindowSwitcherPopup (0x55dc0594be10), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[2668]: == Stack trace for context 0x55dbe9e5e350 ==
gnome-shell[2668]: #0 55dbf94903f0 i resource:///org/gnome/shell/ui/windowManager.js:2097 (7f04b0d3e8b0 @ 410)
gnome-shell[2668]: #1 7ffcd0a84df0 I self-hosted:981 (7f04b0c34160 @ 474)
gnome-shell[2668]: clutter_actor_destroy: assertion 'CLUTTER_IS_ACTOR (self)' failed
gnome-shell[2668]: Object .Gjs_WindowSwitcherPopup (0x55dbf296b2c0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[2668]: == Stack trace for context 0x55dbe9e5e350 ==
gnome-shell[2668]: #0 55dbf2fad380 i resource:///org/gnome/shell/ui/windowManager.js:2097 (7f04b0d3e8b0 @ 410)
gnome-shell[2668]: #1 7ffcd0a84df0 I self-hosted:981 (7f04b0c34160 @ 474)
gnome-shell[2668]: clutter_actor_destroy: assertion 'CLUTTER_IS_ACTOR (self)' failed
systemd[2313]: gnome-terminal-server.service: Main process exited, code=killed, status=15/TERM
systemd[2313]: gnome-terminal-server.service: Succeeded.
gnome-shell[2668]: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
dbus-daemon[2334]: [session uid=1000 pid=2334] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.501' (uid=1000 pid=14625 comm="/usr/bin/gnome-terminal.real --window " label="unconfined")
systemd[2313]: gnome-terminal-server.service: Found left-over process 17793 (mount.ntfs-3g) in control group while starting unit. Ignoring.
systemd[2313]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
systemd[2313]: Starting GNOME Terminal Server...
dbus-daemon[2334]: [session uid=1000 pid=2334] Successfully activated service 'org.gnome.Terminal'
systemd[2313]: Started GNOME Terminal Server.
gnome-shell[2668]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
gnome-shell[2668]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
gnome-shell[2668]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
gnome-shell[2668]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
Thanks !
Edited by Mathieu Tarral