Created attachment 1412408 [details]
File: backtrace

Created attachment 1412409 [details]
File: cgroup

Created attachment 1412410 [details]
File: core_backtrace

Created attachment 1412411 [details]
File: cpuinfo

Created attachment 1412412 [details]
File: dso_list

Created attachment 1412413 [details]
File: environ

Created attachment 1412414 [details]
File: limits

Created attachment 1412415 [details]
File: maps

Created attachment 1412416 [details]
File: mountinfo

Created attachment 1412417 [details]
File: open_fds

Created attachment 1412418 [details]
File: proc_pid_status

Created attachment 1412419 [details]
File: var_log_messages

Similar problem has been detected:

crtl Q to stop Evolution closes Gnome and  i must login again.

reporter:       libreport-2.9.4
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: raise
executable:     /usr/bin/gnome-shell
journald_cursor: s=aca49bea3ce14c1d844b643ac507637f;i=1dc21b;b=a195145abbc14340bc3405e2ddb1067a;m=1875ad17;t=569136f98c96a;x=4cdfc2b854dcbe91
kernel:         4.16.0-300.fc28.x86_64
package:        gnome-shell-3.28.0-1.fc28
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

My system was running under heavy memory load and the swap partition was in use,
which slowed down the general responsiveness. Then, i watched a short clip with mpv.
At the end of the short clip, mpv wanted to close itself as usual and bring me back to
my file browser (thats what mpv always does).
But the system hang up at that moment, for about a minute. The following happened within this minute:
My mouse got frozen on the file browser screen. Then, i got a black screen and a forced restart
of the gnome-shell.

reporter:       libreport-2.9.4
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: raise
executable:     /usr/bin/gnome-shell
journald_cursor: s=f87efbae389943d988591b6aa7c7ed9b;i=250a9;b=59e407289c0b493d8240e9bbd0a633e4;m=1ea0587502;t=5694f568d3528;x=4aaa09496df0ff6f
kernel:         4.16.0-300.fc28.x86_64
package:        gnome-shell-3.28.0-1.fc28
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Created attachment 1418899 [details]
complete backtrace and stuff

zip, z01 - z04

Ignore my created attachment above, i am not able to upload the rest. 400 Bad Request.

So i uploaded the backtrace here:
http://workupload.com/archive/Swa53Qa
Password: RedHat

Well, this hit "Connection to xwayland lost", which seems like it certainly could've come from your 'systemctl isolate multi-user.target' Chris, yeah. Do you have a broader extract of the journal from around the time of the crash than abrt attached?

Unfortunately I do not have persistent logs for that date, I was using storage=volatile.

Similar problem has been detected:

invoke libera office calc

reporter:       libreport-2.9.4
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: raise
executable:     /usr/bin/gnome-shell
journald_cursor: s=89aa729172cf439cb6cf11984ce86e16;i=290c9;b=6a0a5c03fd24426e8f7e1c1b5d48e397;m=1b81c0cc8;t=569d8a7427f44;x=3a7a2cf5e02de926
kernel:         4.16.1-300.fc28.x86_64
package:        gnome-shell-3.28.0-1.fc28
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

The last action I remember before the crash is - closing 'evolution'

reporter:       libreport-2.9.4
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: raise
executable:     /usr/bin/gnome-shell
journald_cursor: s=c6d1a47e3fdb4721a8305ccd59293b81;i=12524d;b=0e858cbb786f4cf694bb338dd998df72;m=eec9d3b30;t=56ac33a11b5b9;x=f4e50bda6517278c
kernel:         4.16.4-300.fc28.x86_64
package:        gnome-shell-3.28.1-1.fc28
reason:         gnome-shell killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

I have been experiencing an unstable F27 installation for several months, with crashes of Xwayland and gnome-shell every day or two, particularly on resuming from suspend (on wayland and xorg). I've been tracking this bug as a possible cause.

I've been running for 10 days without the problem occurring with the workaround in bug #1553979 comment #37 (
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c37 ). I've not seen this level of stability for months.

This is anecdotal and either my original problem or apparent solution may be a misdiagnosis of this bug, however I post here in case others are in the same situation. Apologies to those for who this isn't relevant.

Bug #1553979 is sensitive to memory pressure, which is consistent with my experience of the problem exhibiting more or less frequently as I've changed configuration or behaviour, and potentially as other bugs have been fixed.

I've encountered this problem too, with the same immediate trigger as comment #13: closing Evolution. (This has happened for me more than once.)

journalctl reports:

Process 20583 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 20583:
#0  0x00007f7a08528e4b raise (libpthread.so.0)
#1  0x0000558dd9c4fb83 n/a (/usr/bin/gnome-shell (deleted))
#2  0x00007f7a08528fb0 __restore_rt (libpthread.so.0)
#3  0x00007f7a0a3056d5 _g_log_abort (libglib-2.0.so.0)
#4  0x00007f7a0a3080ac g_log_writer_default (libglib-2.0.so.0)
#5  0x00007f7a0a3062f7 g_log_structured_array (libglib-2.0.so.0)
#6  0x00007f7a0a306d32 g_log_structured_standard (libglib-2.0.so.0)
#7  0x00007f7a07a67b2b _gdk_x11_display_error_event (libgdk-3.so.0)
#8  0x00007f7a07a74993 gdk_x_error (libgdk-3.so.0)
#9  0x00007f7a06f0fec2 _XError (libX11.so.6)
#10 0x00007f7a06f0cd67 handle_error (libX11.so.6)
#11 0x00007f7a06f0ce0d handle_response (libX11.so.6)
#12 0x00007f7a06f0d72d _XEventsQueued (libX11.so.6)
#13 0x00007f7a06eff257 XPending (libX11.so.6)
#14 0x00007f7a07a6ef85 gdk_event_source_prepare (libgdk-3.so.0)
#15 0x00007f7a0a2ff049 g_main_context_prepare (libglib-2.0.so.0)
#16 0x00007f7a0a2ffa3b g_main_context_iterate.isra.21 (libglib-2.0.so.0)
#17 0x00007f7a0a2ffec2 g_main_loop_run (libglib-2.0.so.0)
#18 0x00007f7a087e5b00 n/a (/usr/lib64/libmutter-2.so.0.0.0 (deleted))

This is also logged at:

https://retrace.fedoraproject.org/faf/reports/2129798/

(That grouping of reports is different from the one the original reporter linked to, and it appears the incidence of this crash [mine specifically, that is] is growing.)

I've also looked through bug #1510059, and to answer one of the questions there, no I don't see a corresponding XWayland crash.

(In reply to David H. Gutteridge from comment #22)
> I've encountered this problem too, with the same immediate trigger as
> comment #13: closing Evolution. (This has happened for me more than once.)
> 
> journalctl reports:
> 
> Process 20583 (gnome-shell) of user 1000 dumped core.
> Stack trace of thread 20583:
> #0  0x00007f7a08528e4b raise (libpthread.so.0)
> #1  0x0000558dd9c4fb83 n/a (/usr/bin/gnome-shell (deleted))
> #2  0x00007f7a08528fb0 __restore_rt (libpthread.so.0)
> #3  0x00007f7a0a3056d5 _g_log_abort (libglib-2.0.so.0)
> #4  0x00007f7a0a3080ac g_log_writer_default (libglib-2.0.so.0)
> #5  0x00007f7a0a3062f7 g_log_structured_array (libglib-2.0.so.0)
> #6  0x00007f7a0a306d32 g_log_structured_standard (libglib-2.0.so.0)
> #7  0x00007f7a07a67b2b _gdk_x11_display_error_event (libgdk-3.so.0)
> #8  0x00007f7a07a74993 gdk_x_error (libgdk-3.so.0)
> #9  0x00007f7a06f0fec2 _XError (libX11.so.6)
> #10 0x00007f7a06f0cd67 handle_error (libX11.so.6)
> #11 0x00007f7a06f0ce0d handle_response (libX11.so.6)
> #12 0x00007f7a06f0d72d _XEventsQueued (libX11.so.6)
> #13 0x00007f7a06eff257 XPending (libX11.so.6)
> #14 0x00007f7a07a6ef85 gdk_event_source_prepare (libgdk-3.so.0)
> #15 0x00007f7a0a2ff049 g_main_context_prepare (libglib-2.0.so.0)
> #16 0x00007f7a0a2ffa3b g_main_context_iterate.isra.21 (libglib-2.0.so.0)
> #17 0x00007f7a0a2ffec2 g_main_loop_run (libglib-2.0.so.0)
> #18 0x00007f7a087e5b00 n/a (/usr/lib64/libmutter-2.so.0.0.0 (deleted))
> 
> This is also logged at:
> 
> https://retrace.fedoraproject.org/faf/reports/2129798/
> 
> (That grouping of reports is different from the one the original reporter
> linked to, and it appears the incidence of this crash [mine specifically,
> that is] is growing.)
> 
> I've also looked through bug #1510059, and to answer one of the questions
> there, no I don't see a corresponding XWayland crash.

I'm seeing the same issue here. There is nothing about XWayland in the logs and no indication why this happens.

*** Bug 1641343 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.