gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap (invalid Pixmap parameter)"] from ... meta_pre_paint_func()

[laurent Thomas]

https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee
https://gitlab.gnome.org/GNOME/mutter/issues/253

---

don't know why, maybe related to printer

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 14 10:02:43 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'libreoffice-calc.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-02-12 (29 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _g_log_abort (breakpoint=breakpoint@entry=1) at ../../../../glib/gmessages.c:583
 g_log_writer_default (log_level=6, log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7fff1a1f0800, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../../glib/gmessages.c:2735
 g_log_structured_array (log_level=G_LOG_LEVEL_ERROR, fields=0x7fff1a1f0800, n_fields=6) at ../../../../glib/gmessages.c:1970
 g_log_structured_standard (log_domain=log_domain@entry=0x7f90daeaf28e "Gdk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f90daecda78 "../../../../../gdk/x11/gdkdisplay-x11.c", line=line@entry=0x7f90daecd4cf "2766", func=func@entry=0x7f90daece190 <__func__.74387> "_gdk_x11_display_error_event", message_format=message_format@entry=0x7f90daece50b "%s") at ../../../../glib/gmessages.c:2027
 _gdk_x11_display_error_event (display=display@entry=0x55fd45c2f110, error=error@entry=0x7fff1a1f0e50) at ../../../../../gdk/x11/gdkdisplay-x11.c:2766

[Daniel van Vugt (vanvugt)]

Looks like bug 1691701. Only the stack trace changed a little in 18.04 so we have this new bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Also tracking in:
https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee

[Cristian Aravena Romero (caravena)]

https://gitlab.gnome.org/GNOME/gnome-shell/issues/456

[Daniel van Vugt (vanvugt)]

Now
https://gitlab.gnome.org/GNOME/mutter/issues/253

[Cristian Aravena Romero (caravena)]

Hello,

How I do this?
"Could you please set GDK_SYNCHRONIZE=1 somewhere in the environment"

Regards,
--
Cristian Aravena Romero (caravena)

[Daniel van Vugt (vanvugt)]

You add a line to /etc/environment:

GDK_SYNCHRONIZE=1

and then reboot.

[Cristian Aravena Romero (caravena)]

Hello Daniel van Vugt,

I added the variable 'GDK_SYNCHRONIZE=1' in my work environment, however, the report was marked in the same way as replica ... As if it were an identical report to LP: #1755779

See LP: #1788613 This report has the variable 'GDK_SYNCHRONIZE=1'

Please tell me what to do ... I currently have _usr_bin_gnome-shell.1000.crash in case I need...

Kind regards,
--
Cristian Aravena Romero (caravena)

[Daniel van Vugt (vanvugt)]

If you have a crash file then please always use 'ubuntu-bug' to send it:

  ubuntu-bug _usr_bin_gnome-shell.1000.crash

That will create a new bug.

[Cristian Aravena Romero (caravena)]

Hello,

All over again ... Is 'GDK_SYNCHRONIZE = 1' okay?

Best regards,
--
Cristian Aravena Romero (caravena)

[Daniel van Vugt (vanvugt)]

Zero crash reports in GNOME versions after 3.36 so consider it fixed.