Ubuntu

gnome-shell crashes when switching from workspace that is running Android emulator (QEMU)

Asked by FixMaker

I'm running Ubuntu 18.04 LTS (latest updates).

I can switch between Gnome's workspaces using Ctrl+Alt+<up and down>, no problem. However, if I run the Android emulator (that uses QEMU) on the current workspace, and then try and switch to a different workspace, the screen will "blank out" as if the window manager has been restarted. Sometimes it will crash completely and return me to the logon screen, and I have to log back on to start a new session.

/var/log/syslog has the following lines, each time I try an switch from a workspace that is running the Android emulator:

------------------------------------------------------------------------------------------------

Jan 18 20:13:08 astux /usr/lib/gdm3/gdm-x-session[1851]: (EE) modeset(0): Failed to make 16bpp pixmap exportable
Jan 18 20:13:09 astux kernel: [ 256.578863] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.
Jan 18 20:13:08 astux /usr/lib/gdm3/gdm-x-session[1851]: (EE) modeset(0): Failed to make 16bpp pixmap exportable
Jan 18 20:13:09 astux org.gnome.Shell.desktop[1970]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2400002 specified for 0x2400005 (Android Em).
Jan 18 20:13:14 astux org.gnome.Shell.desktop[1970]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2400002 specified for 0x240000a (Emulator).
Jan 18 20:13:43 astux gnome-shell[1970]: Object Meta.WindowActor (0x56027b161780), 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
Jan 18 20:13:43 astux kernel: [ 290.679274] show_signal_msg: 44 callbacks suppressed
Jan 18 20:13:43 astux kernel: [ 290.679276] gnome-shell[1970]: segfault at 28 ip 00007f290e0bafe0 sp 00007ffdd6b37308 error 4 in libmutter-2.so.0.0.0[7f290e037000+157000]
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: == Stack trace for context 0x56027959e330 ==
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #0 0x56027994ccf8 i resource:///org/gnome/shell/ui/windowManager.js:1787 (0x7f28dc024670 @ 113)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #1 0x7ffdd6b382c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f28dc3b5de0 @ 71)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #2 0x56027994cc70 i resource:///org/gnome/shell/ui/tweener.js:112 (0x7f28dc3c8e68 @ 37)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #3 0x7ffdd6b39d30 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f28dc3d2b38 @ 54)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #4 0x7ffdd6b39e80 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f28dc3d2bc0 @ 1626)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #5 0x7ffdd6b39f30 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f28dc3d2c48 @ 100)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #6 0x7ffdd6b39fc0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f28dc3d2cd0 @ 10)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #7 0x7ffdd6b3a0b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f28dc3d2230 @ 386)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #8 0x7ffdd6b3a160 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f28dc3cf808 @ 159)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #9 0x7ffdd6b3a1c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f28dc3b5de0 @ 71)
Jan 18 20:13:43 astux org.gnome.Shell.desktop[1970]: #10 0x7ffdd6b3a260 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f28dc3cf780 @ 15)
Jan 18 20:13:43 astux gnome-session[1866]: gnome-session-binary[1866]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jan 18 20:13:43 astux gnome-session-binary[1866]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jan 18 20:13:43 astux /usr/lib/gdm3/gdm-x-session[1851]: (II) modeset(0): EDID vendor "CMN", prod id 4961
Jan 18 20:13:43 astux /usr/lib/gdm3/gdm-x-session[1851]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 18 20:13:43 astux /usr/lib/gdm3/gdm-x-session[1851]: (II) modeset(0): Modeline "1920x1080"x0.0 138.78 1920 1966 1996 2080 1080 1082 1086 1112 -hsync -vsync (66.7 kHz eP)
Jan 18 20:13:43 astux /usr/lib/gdm3/gdm-x-session[1851]: (II) modeset(0): Modeline "1920x1080"x0.0 92.52 1920 1966 1996 2080 1080 1082 1086 1112 -hsync -vsync (44.5 kHz e)
Jan 18 20:13:43 astux gsd-media-keys[2130]: g_variant_get_va: assertion 'value != NULL' failed
Jan 18 20:13:43 astux gsd-media-keys[2130]: g_variant_unref: assertion 'value != NULL' failed
Jan 18 20:13:43 astux org.gnome.Shell.desktop[2557]: current session already has an ibus-daemon.
Jan 18 20:13:44 astux dbus-daemon[1193]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.107' (uid=1000 pid=2557 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 18 20:13:44 astux systemd[1]: Starting Location Lookup Service...
Jan 18 20:13:44 astux dbus-daemon[1193]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Jan 18 20:13:44 astux systemd[1]: Started Location Lookup Service.
Jan 18 20:13:44 astux wpa_supplicant[1225]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Jan 18 20:13:44 astux gnome-shell[2557]: Telepathy is not available, chat integration will be disabled.
Jan 18 20:13:44 astux gnome-shell[2557]: JS WARNING: [/<email address hidden>/appIcons.js 1028]: unreachable code after return statement
Jan 18 20:13:44 astux bluetoothd[1228]: Failed to set mode: Blocked through rfkill (0x12)
Jan 18 20:13:44 astux gnome-shell[2557]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.71/org/ayatana/NotificationItem/software_update_available
Jan 18 20:13:44 astux gnome-shell[2557]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
Jan 18 20:13:44 astux gnome-shell[2557]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Jan 18 20:13:46 astux gnome-shell[2557]: GNOME Shell started at Fri Jan 18 2019 20:13:44 GMT

------------------------------------------------------------------------------------------------

From the logs, it looks like the problem is with gnome-shell (specifically libmutter). Interestingly, this only seems to happen when the Android emulator window is open --- if it's minimized, then the problem doesn't manifest itself.

Also, I don't remember seeing this problem before. It seems to have started after I installed the latest updates yesterday (although I can't be certain that this is the cause of the problem). Previously, I was able to switch between workspaces that contained the Android emulator with no problem.

Any suggestions how I should progress this? Should I report a bug against gnome-shell, or something else?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Yes please log a bug against gnome-shell

You can do this by running:

ubuntu-bug gnome-shell

to start the process

Revision history for this message
Xhelas (xhelas) said : 		#2

Same bug for me. Quite annoying.

Revision history for this message
Jean-Francois Turcot (jfturcot) said : 		#3

I am also having this problem, it only started recently.

Revision history for this message
Khalil Laleh (khalilst) said : 		#4

Same for me at ubuntu 18.04.1, gdm3, GeForce MX150 (nvidia-driver-390).
When I have opening Android Emulator, switching between workspaces causes to system crash and logout!

Revision history for this message
Khalil Laleh (khalilst) said : 		#5

I found a solution (not ideal but works).
1. Disable Desktop Animations using dconf-editor. Set /org/gnome/desktop/interface/enable-animations => false.

2. (Optional - only for better performance) Change Android Emulator/Settings/'Send Keyborad Shortcut to' from "Emulator Controls (Default)" to "Virtual Device".

However I think there's a bug in gdm3 updates. Also I noticed that the mouse clicks not working in login screen. Only keyboard works.

Revision history for this message
Xhelas (xhelas) said : 		#6

Thank you Khalil for the work around! Works well on my setup.

Revision history for this message
FixMaker (fixmaker) said : 		#7

@khalilst's solution seems to work for me too, but I agree it's not ideal.

Looks like a bug has been raised against this issue here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812527

Revision history for this message
lgngr (lgngr) said : 		#8

I had the same problem due to the recently update... the solution it work for me

Revision history for this message
ted jenson (tedjenson90) said : 		#9

I had the same problem. Thanks for your response. It worked for me.

Can you help with this problem?

Provide an answer of your own, or ask FixMaker for more information if necessary.

To post a message you must log in.