gnome-shell crashed with signal 5 in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from [stack of bug 1505409]

[José Henrique de Almeida Gomes]

gnome-shell crashed with signal 5 in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from [stack of bug 1505409]

This bug is really a duplicate of bug 1505409, but is being kept separate so that the bots can automatically deduplicate new bug reports as they come in (which will now match this bug instead of bug 1505409).

---

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Nov 16 06:57:59 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-11-14 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: Upgraded to bionic on 2017-11-15 (1 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:554
 g_log_default_handler (log_domain=<optimized out>, log_level=<optimized out>, message=<optimized out>, unused_data=<optimized out>) at ../../../../glib/gmessages.c:3051
 default_log_handler (log_domain=log_domain@entry=0x7f3c825c0b93 "mutter", log_level=log_level@entry=6, message=message@entry=0x5601485ae980 "Connection to xwayland lost", data=data@entry=0x0) at ../src/main.c:315
 g_logv (log_domain=0x7f3c825c0b93 "mutter", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fffe91a3f30) at ../../../../glib/gmessages.c:1341
 g_log (log_domain=log_domain@entry=0x7f3c825c0b93 "mutter", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f3c825d1af0 "Connection to xwayland lost") at ../../../../glib/gmessages.c:1403

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[dino99 (9d9)]

@seb128

- reproducible : yes multiple users affected
- the gnome-bug reported is pointing a possible wayland/mutter cause, but my report lp:1736512 is opened with gnome on xorg session.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1505409, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Daniel van Vugt (vanvugt)]

This bug is really a duplicate of bug 1505409, but is being kept separate so that the bots can automatically deduplicate new bug reports as they come in. New reports will match this bug automatically, instead of a human having to point them to bug 1505409.

The offending stack trace changed around 18.04's 3.26.2-0ubuntu1, but it's really still bug 1505409.

So please don't mark this one as a duplicate. It's being used as fly paper.

[Daniel van Vugt (vanvugt)]

Scrap that plan. It's not working. I guess the stack trace signature here is too old to much current crashes any more.

See bug 1505409 instead.

[Daniel van Vugt (vanvugt)]

*too old to match