Bug 1516466 - GNOME Shell crashes when moving window in GNOME application overview
Summary: GNOME Shell crashes when moving window in GNOME application overview
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-22 16:48 UTC by rugk
Modified: 2023-09-14 04:12 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 20:55:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Wayland report fails as backtrace is broken (161.55 KB, image/png)
2017-11-22 16:48 UTC, rugk
no flags Details
Abrt reporting crash (58.29 KB, image/png)
2017-12-12 22:53 UTC, rugk
no flags Details
manually added from abrt dir (10.35 KB, text/plain)
2017-12-12 23:02 UTC, rugk
no flags Details

Description rugk 2017-11-22 16:48:52 UTC
Created attachment 1357673 [details]
Wayland report fails as backtrace is broken

Description of problem: Since the upgrade to Fedora 27 Wayland often crashes, so I am logged out and must login again.


How reproducible: regularly.


Steps to Reproduce:
I suspect it could be related to when I have Firefox 57 running and go to the application menu (overview). But maybe it is unrelated, but at least the animation when showing the application overview is IIRC often the last thing I can see.

Actual results:
1. A few seconds the screen freezes.
2. I am logged out, gdm is shown.
3. Login again…
4. (As in the screenshot) Abrt shows a crash.
5. When you try to report it, it says the backtrace is "not usable".

Note that in the Screenshot Wayland-xorg or so crashes. This is rather rare, in most cases I saw that Wayland itself crashed (that was the name shown in abrt).

Expected results: Do not crash.


Additional info:

Nouvou graphics
This did *not* happen with Fedora 26.

In the one case I just experienced I also had problems with pulseaudio after logging in again: After openening Firefox it could not recognize PulseAudio, and showed me a note to install PulseAudio.

"Important system logs":
17:18:05 setroubleshootd: SELinux is preventing snapd from getattr access on the lnk_file /etc/pki/tls/certs/ca-bundle.crt. For complete SELinux messages run: sealert -l 9cb8f0c9-ec37-4490-be62-97a6cffc550d
17:16:05 systemd: Failed to start flatpak-org.mozilla.FirefoxDevEdition-3635.scope.
17:07:41 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
17:07:39 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
17:07:33 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
17:07:32 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
17:07:30 abrtd: '/var/spool/abrt/ccpp-2017-07-30-11:57:17.340786-1525' is not a problem directory
17:07:29 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
17:07:29 avahi-daemon: chroot.c: open() failed: No such file or directory
18:07:25 systemd-tty-ask: Failed to show password: Bad message

Comment 1 rugk 2017-11-29 23:29:54 UTC
That is really serious as it crashes in the middle of nothing, destroying work and Firefox sessions.

Indeed I can confirm it may be related to Firefox, but in any case it happens after you move your mouse to the upper right to switch applications, then you more or less see the animation and it crashes. Maybe it is some graphic driver issue?

Also, BTW, I can reliably reproduce it after it crashed once. I usually then login, re-open Firefox and directly go into the upper left to switch applications. Then it crashes again…
I.e. if it crashed once and you are fast to login and reproduce it again, it also crashes again. So I just have to wait a few seconds or so after the login, then I can avoid the crash. (It *may* also not crash when using the super key instead of the mouse, but I am not yet sure of that.)

Comment 2 rugk 2017-12-01 13:47:52 UTC
Correction:
1. It *does* happen when using the super key.
2. It really only seems to happen with Firefox…

Comment 3 rugk 2017-12-01 13:48:08 UTC
…aand it is always XWayland, which crashes.

Comment 4 rugk 2017-12-04 19:04:58 UTC
Report seems to be https://retrace.fedoraproject.org/faf/reports/1911767/

Comment 5 rugk 2017-12-12 22:29:11 UTC
So… actually… it is not really related to Firefox nor to XWayland.
Because it also happens 

I could currently just only reproduce it **on the GNOME application overview** mode.

STR:
1. Login to GNOME.
2. Open a window. (e.g. gedit or – as said – Firefox).
3. Switch to overview ("applications") mode.
4.

Comment 6 rugk 2017-12-12 22:45:34 UTC
4. Fastly move your cursor around.

So as it only happens on the "on the GNOME application overview" I choose the component "GNOME desktop" here. Also opened a GNOME issue at https://bugzilla.gnome.org/show_bug.cgi?id=791544.

As the "Mesa" is also mentioned in the crash report I opened: https://bugs.freedesktop.org/show_bug.cgi?id=104233

Comment 7 rugk 2017-12-12 22:53:12 UTC
Created attachment 1366989 [details]
Abrt reporting crash

Comment 8 rugk 2017-12-12 23:01:34 UTC
To reiterate: You need:
* to have the GNOME overview open
* move your mouse pointer fast enough
* any application open (I guess)

BTW, it is best reproducible with two monitors:
0. As said, of course still be in the overview mode. (it does *not* work, otherwise!)
1. Grab that one window on that one screen. Fastly move it to the other screen and drop it! -> Freeze/crash

Some other observations:
* These "broken crash reports" always disappear from the abrt list/window once another crash with them happens, or (I think) you just logout and login again. (see screenshot)
* I am not sure abrt always shows me the same name of the crashed application. I think at least in the notification it shows me XWayland, Xorg or "some component" more or less randomly. In any case is the link to the server crash report (retrace) always the same, so it is always the same issue.
If you want one ID, here it is, e.g.: /var/spool/abrt/ccpp-2017-12-12-23:48:55.122995-29804

Some data grabbed from abrt report dir:
Xwayland killed by SIGABRT
/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6

Name:	Xwayland
Umask:	0002
State:	S (sleeping)
Tgid:	29804
Ngid:	0
Pid:	29804
PPid:	1
TracerPid:	0
Uid:	1000	1000	1000	1000
Gid:	1000	1000	1000	1000
FDSize:	64
Groups:	10 1000 
NStgid:	29804
NSpid:	29804
NSpgid:	29703
NSsid:	29703
VmPeak:	  832168 kB
VmSize:	  629140 kB
VmLck:	       0 kB
VmPin:	       0 kB
VmHWM:	   92064 kB
VmRSS:	   67352 kB
RssAnon:	   21228 kB
RssFile:	   29620 kB
RssShmem:	   16504 kB
VmData:	   72408 kB
VmStk:	     132 kB
VmExe:	    2088 kB
VmLib:	   69588 kB
VmPTE:	     528 kB
VmPMD:	      16 kB
VmSwap:	       0 kB
HugetlbPages:	       0 kB
Threads:	6
SigQ:	0/31509
SigPnd:	0000000000000000
ShdPnd:	0000000000000000
SigBlk:	000000000a392000
SigIgn:	0000000000001000
SigCgt:	00000001c18064cf
CapInh:	0000000000000000
CapPrm:	0000000000000000
CapEff:	0000000000000000
CapBnd:	0000003fffffffff
CapAmb:	0000000000000000
NoNewPrivs:	0
Seccomp:	0
Cpus_allowed:	f
Cpus_allowed_list:	0-3
Mems_allowed:	00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
Mems_allowed_list:	0
voluntary_ctxt_switches:	367604
nonvoluntary_ctxt_switches:	27160

uReport: BTHASH=18d455894df7d9531ace5a146f495863b59721d1
ABRT Server: URL=https://retrace.fedoraproject.org/faf/reports/bthash/18d455894df7d9531ace5a146f495863b59721d1

Comment 9 rugk 2017-12-12 23:02:39 UTC
Created attachment 1366994 [details]
manually added from abrt dir

Comment 10 Daniel Stone 2017-12-13 13:29:20 UTC
At a guess, this is an issue with Mutter rather than Xwayland. Generally, when xwl_read_events fails, this means that it has been disconnected from Mutter (GNOME Shell), either because of an error or because it has crashed.

If you can get the logs from 'journalctl --user', you should see all the messages from the gnome-shell process.

Comment 11 rugk 2017-12-15 13:57:47 UTC
When I run this I only get messy logs about something else.

So I just reporuced it and then looked into the GNOME "system protocol" application (filtered for gnome-shell), and I only see that:

14:50:54 gnome-shell: Received error from DBus search provider org.gnome.Calendar.desktop: Gio.IOErrorEnum: Zeitüberschreitung wurde erreicht
14:50:30 dbus-daemon: [session uid=1000 pid=6329] Activating service name='org.gnome.Logs' requested by ':1.282' (uid=1000 pid=18718 comm="/usr/bin/gnome-shell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
14:50:29 gnome-shell: Received error from DBus search provider org.gnome.Epiphany.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.EpiphanySearchProvider was not provided by any .service files
14:50:29 gnome-shell: Received error from DBus search provider org.gnome.Epiphany.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.EpiphanySearchProvider was not provided by any .service files
14:50:29 gnome-shell: Received error from DBus search provider org.gnome.Epiphany.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.EpiphanySearchProvider was not provided by any .service files
14:50:29 dbus-daemon: [session uid=1000 pid=6329] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.282' (uid=1000 pid=18718 comm="/usr/bin/gnome-shell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
14:50:28 gnome-shell: clutter-actor.c:10049: Actor 'ClutterText' tried to allocate a size of 332,00 x -2147483648,00
14:49:54 gnome-software: running get-installed[…]

----

Ohh, wait, further below there is something:

4:49:05 systemd-coredum: Process 6463 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 6463:
#0  0x00007fef247df630 st_theme_node_reduce_border_radius (libst-1.0.so)
#1  0x00007fef247e1d69 st_theme_node_paint_borders (libst-1.0.so)
#2  0x00007fef247e45f9 st_theme_node_paint (libst-1.0.so)
#3  0x00007fef247e7d70 st_widget_paint_background (libst-1.0.so)
#4  0x00007fef247cee4a st_label_paint (libst-1.0.so)
#5  0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#6  0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#7  0x00007fef25a22050 clutter_actor_real_paint (libmutter-clutter-1.so)
#8  0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#9  0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#10 0x00007fef25a22050 clutter_actor_real_paint (libmutter-clutter-1.so)
#11 0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#12 0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#13 0x00007fef25a22050 clutter_actor_real_paint (libmutter-clutter-1.so)
#14 0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#15 0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#16 0x00007fef25a22050 clutter_actor_real_paint (libmutter-clutter-1.so)
#17 0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#18 0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#19 0x00007fef27670094 shell_generic_container_paint (libgnome-shell.so)
#20 0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#21 0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#22 0x00007fef25a74d4a clutter_stage_paint (libmutter-clutter-1.so)
#23 0x00007fef25283932 meta_stage_paint (libmutter-1.so.0)
#24 0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)
#25 0x00007fef25a21dc4 clutter_actor_paint.part.44 (libmutter-clutter-1.so)
#26 0x00007fef25a78e9f clutter_stage_do_paint_view (libmutter-clutter-1.so)
#27 0x00007fef25a79193 _clutter_stage_paint_view (libmutter-clutter-1.so)
#28 0x00007fef25a0bf44 paint_stage (libmutter-clutter-1.so)
#29 0x00007fef25a0c0e3 clutter_stage_cogl_redraw_view (libmutter-clutter-1.so)
#30 0x00007fef25a0d2cb clutter_stage_cogl_redraw (libmutter-clutter-1.so)
#31 0x00007fef2530fc0e meta_stage_native_redraw (libmutter-1.so.0)
#32 0x00007fef25a75d07 _clutter_stage_do_update (libmutter-clutter-1.so)
#33 0x00007fef25a618a9 clutter_clock_dispatch (libmutter-clutter-1.so)
#34 0x00007fef26d98bb7 g_main_context_dispatch (libglib-2.0.so.0)
#35 0x00007fef26d98f60 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
#36 0x00007fef26d99272 g_main_loop_run (libglib-2.0.so.0)
#37 0x00007fef252b34fc meta_run (libmutter-1.so.0)
#38 0x000055c0c377542c main (gnome-shell)
#39 0x00007fef24c2c03a __libc_start_main (libc.so.6)
#40 0x000055c0c377556a _start (gnome-shell)

Stack trace of thread 6735:
#0  0x00007fef24d24fd6 epoll_pwait (libc.so.6)
#1  0x00007feea39456e3 loop_iterate (libspa-support.so)
#2  0x00007fef192bfba8 do_loop (libpipewire-0.1.so.0)
#3  0x00007fef24ff7609 start_thread (libpthread.so.0)
#4  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 10416:
#0  0x00007fef24d24fd6 epoll_pwait (libc.so.6)
#1  0x00007feea39456e3 loop_iterate (libspa-support.so)
#2  0x00007fef192bfba8 do_loop (libpipewire-0.1.so.0)
#3  0x00007fef24ff7609 start_thread (libpthread.so.0)
#4  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6520:
#0  0x00007fef24d188bb __poll (libc.so.6)
#1  0x00007feef1e2d6f1 poll_func (libpulse.so.0)
#2  0x00007feef1e1f0b0 pa_mainloop_poll (libpulse.so.0)
#3  0x00007feef1e1f740 pa_mainloop_iterate (libpulse.so.0)
#4  0x00007feef1e1f7d0 pa_mainloop_run (libpulse.so.0)
#5  0x00007feef1e2d639 thread (libpulse.so.0)
#6  0x00007feef1bccac8 internal_thread_func (libpulsecommon-11.1.so)
#7  0x00007fef24ff7609 start_thread (libpthread.so.0)
#8  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6521:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6526:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6474:
#0  0x00007fef24d188bb __poll (libc.so.6)
#1  0x00007fef26d98ed9 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
#2  0x00007fef26d98fec g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fef1090a42d dconf_gdbus_worker_thread (libdconfsettings.so)
#4  0x00007fef26dc04c6 g_thread_proxy (libglib-2.0.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6484:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007feef74693cb util_queue_thread_func (nouveau_dri.so)
#2  0x00007feef74692e7 impl_thrd_routine (nouveau_dri.so)
#3  0x00007fef24ff7609 start_thread (libpthread.so.0)
#4  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6523:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6527:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6470:
#0  0x00007fef24d188bb __poll (libc.so.6)
#1  0x00007fef26d98ed9 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
#2  0x00007fef26d99272 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007fef27381b36 gdbus_shared_thread_func (libgio-2.0.so.0)
#4  0x00007fef26dc04c6 g_thread_proxy (libglib-2.0.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6524:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6525:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 18501:
#0  0x00007fef24d1f0d9 syscall (libc.so.6)
#1  0x00007fef26dde66a g_cond_wait_until (libglib-2.0.so.0)
#2  0x00007fef26d6d381 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
#3  0x00007fef26d6d93c g_async_queue_timeout_pop (libglib-2.0.so.0)
#4  0x00007fef26dc0f6e g_thread_pool_thread_proxy (libglib-2.0.so.0)
#5  0x00007fef26dc04c6 g_thread_proxy (libglib-2.0.so.0)
#6  0x00007fef24ff7609 start_thread (libpthread.so.0)
#7  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6522:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6469:
#0  0x00007fef24d188bb __poll (libc.so.6)
#1  0x00007fef26d98ed9 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
#2  0x00007fef26d98fec g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fef26d99031 glib_worker_main (libglib-2.0.so.0)
#4  0x00007fef26dc04c6 g_thread_proxy (libglib-2.0.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

Stack trace of thread 6528:
#0  0x00007fef24ffdc3b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fef1d261a24 _ZN2js17ConditionVariable4waitERNS_9LockGuardINS_5MutexEEE (libmozjs-52.so.0)
#2  0x00007fef1d261c95 _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-52.so.0)
#3  0x00007fef1d65a3d3 _ZN2js12HelperThread10threadLoopEv (libmozjs-52.so.0)
#4  0x00007fef1d67b9f2 _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE5StartES2_ (libmozjs-52.so.0)
#5  0x00007fef24ff7609 start_thread (libpthread.so.0)
#6  0x00007fef24d24e6f __clone (libc.so.6)

14:49:05 dbus-daemon: [system] Rejected send message, 0 matched rules; type="error", sender=":1.1" (uid=0 pid=1182 comm="/usr/lib/systemd/systemd-logind " label="system_u:system_r:systemd_logind_t:s0") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.22" (uid=42 pid=1441 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
14:49:05 gnome-shell: Failed to apply DRM plane transform 0: Das Argument ist ungültig
14:49:02 kernel: gnome-shell[6463]: segfault at 80 ip 00007fef247df630 sp 00007ffe06c93018 error 4 in libst-1.0.so[7fef247af000+4d000]
14:49:02 gnome-shell: clutter_paint_volume_set_height: assertion 'height >= 0.0f' failed

So it really may be gnome-shell…

Comment 12 rugk 2017-12-21 10:09:47 UTC
BTW can anyone link https://retrace.fedoraproject.org/faf/reports/1973816/ to this ticket? Currently it still says "An owning problem doesn't exist yet.", which is not true…

Comment 13 rugk 2018-01-30 21:34:01 UTC
BTW maybe this issue is related to some freezing in Nautilus, too.

In https://gitlab.gnome.org/GNOME/nautilus/issues/214 I was asked to provide some info and saw it actually presented me some stacktrace about this issue.

Does anyone (@daniel?) have any more ideas/steps I can do here?
And, BTW, the link on retrace.fedoraproject.org is still missing…

I can provide the coredump listed in the output below to a dev, if it is useful.

$ coredumpctl gdb
           PID: 2136 (Xwayland)
           UID: 1000 (********)
           GID: 1000 (********)
        Signal: 6 (ABRT)
     Timestamp: Tue 2018-01-30 21:22:16 CET (56min ago)
  Command Line: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6
    Executable: /usr/bin/Xwayland
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (********)
       Boot ID: 82a7********** (don't know whether this is sensitive)
    Machine ID: 8608********** (don't know whether this is sensitive)
      Hostname: ********
       Storage: /var/lib/systemd/coredump/core.Xwayland.1000.82a78033708d4cb6a1709b682ee9be24.2136.1517343736000000.lz4
       Message: Process 2136 (Xwayland) of user 1000 dumped core.

                Stack trace of thread 2136:
                #0  0x00007f8bf434c66b raise (libc.so.6)
                #1  0x00007f8bf434e381 abort (libc.so.6)
                #2  0x0000000000594d3a OsAbort (Xwayland)
                #3  0x0000000000599f03 AbortServer (Xwayland)
                #4  0x000000000059ad25 FatalError (Xwayland)
                #5  0x00000000004233ad xwl_read_events (Xwayland)
                #6  0x00000000005928b1 ospoll_wait (Xwayland)
                #7  0x000000000058c0bb WaitForSomething (Xwayland)
                #8  0x0000000000557ed3 Dispatch (Xwayland)
                #9  0x000000000055c170 dix_main (Xwayland)
                #10 0x00007f8bf433600a __libc_start_main (libc.so.6)
                #11 0x0000000000422a9a _start (Xwayland)

                Stack trace of thread 2137:
                #0  0x00007f8bf4705cbb pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f8bf0578d8b util_queue_thread_func (nouveau_dri.so)
                #2  0x00007f8bf0578ca7 impl_thrd_routine (nouveau_dri.so)
                #3  0x00007f8bf46ff61b start_thread (libpthread.so.0)
                #4  0x00007f8bf442c98f __clone (libc.so.6)

                Stack trace of thread 2139:
                #0  0x00007f8bf4705cbb pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f8bf09cd03b thread_function (nouveau_dri.so)
                #2  0x00007f8bf09cceb7 impl_thrd_routine (nouveau_dri.so)
                #3  0x00007f8bf46ff61b start_thread (libpthread.so.0)
                #4  0x00007f8bf442c98f __clone (libc.so.6)

                Stack trace of thread 2141:
                #0  0x00007f8bf4705cbb pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f8bf09cd03b thread_function (nouveau_dri.so)
                #2  0x00007f8bf09cceb7 impl_thrd_routine (nouveau_dri.so)
                #3  0x00007f8bf46ff61b start_thread (libpthread.so.0)
                #4  0x00007f8bf442c98f __clone (libc.so.6)

                Stack trace of thread 2138:
                #0  0x00007f8bf4705cbb pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f8bf09cd03b thread_function (nouveau_dri.so)
                #2  0x00007f8bf09cceb7 impl_thrd_routine (nouveau_dri.so)
                #3  0x00007f8bf46ff61b start_thread (libpthread.so.0)
                #4  0x00007f8bf442c98f __clone (libc.so.6)

                Stack trace of thread 2140:
                #0  0x00007f8bf4705cbb pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f8bf09cd03b thread_function (nouveau_dri.so)
                #2  0x00007f8bf09cceb7 impl_thrd_routine (nouveau_dri.so)
                #3  0x00007f8bf46ff61b start_thread (libpthread.so.0)
                #4  0x00007f8bf442c98f __clone (libc.so.6)

GNU gdb (GDB) Fedora 8.0.1-33.fc27
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/Xwayland...Reading symbols from /usr/bin/Xwayland...(no debugging symbols found)...done.
(no debugging symbols found)...done.
[New LWP 2136]
[New LWP 2137]
[New LWP 2139]
[New LWP 2141]
[New LWP 2138]
[New LWP 2140]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f8bf434c66b in raise () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f8bf766fa80 (LWP 2136))]
Missing separate debuginfos, use: dnf debuginfo-install xorg-x11-server-Xwayland-1.19.6-2.fc27.x86_64
(gdb) thread apply all bt

Thread 6 (Thread 0x7f8be94a1700 (LWP 2140)):
#0  0x00007f8bf4705cbb in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007f8bf09cd03b in thread_function () from /usr/lib64/dri/nouveau_dri.so
#2  0x00007f8bf09cceb7 in impl_thrd_routine ()
   from /usr/lib64/dri/nouveau_dri.so
#3  0x00007f8bf46ff61b in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8bf442c98f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8bea4a3700 (LWP 2138)):
#0  0x00007f8bf4705cbb in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007f8bf09cd03b in thread_function () from /usr/lib64/dri/nouveau_dri.so
#2  0x00007f8bf09cceb7 in impl_thrd_routine ()
   from /usr/lib64/dri/nouveau_dri.so
#3  0x00007f8bf46ff61b in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8bf442c98f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8be8ca0700 (LWP 2141)):
#0  0x00007f8bf4705cbb in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007f8bf09cd03b in thread_function () from /usr/lib64/dri/nouveau_dri.so
---Type <return> to continue, or q <return> to quit---
#2  0x00007f8bf09cceb7 in impl_thrd_routine ()
   from /usr/lib64/dri/nouveau_dri.so
#3  0x00007f8bf46ff61b in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8bf442c98f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f8be9ca2700 (LWP 2139)):
#0  0x00007f8bf4705cbb in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007f8bf09cd03b in thread_function () from /usr/lib64/dri/nouveau_dri.so
#2  0x00007f8bf09cceb7 in impl_thrd_routine ()
   from /usr/lib64/dri/nouveau_dri.so
#3  0x00007f8bf46ff61b in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8bf442c98f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f8bebafa700 (LWP 2137)):
#0  0x00007f8bf4705cbb in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x00007f8bf0578d8b in util_queue_thread_func ()
   from /usr/lib64/dri/nouveau_dri.so
#2  0x00007f8bf0578ca7 in impl_thrd_routine ()
   from /usr/lib64/dri/nouveau_dri.so
#3  0x00007f8bf46ff61b in start_thread () from /lib64/libpthread.so.0
#4  0x00007f8bf442c98f in clone () from /lib64/libc.so.6
---Type <return> to continue, or q <return> to quit---

Thread 1 (Thread 0x7f8bf766fa80 (LWP 2136)):
#0  0x00007f8bf434c66b in raise () from /lib64/libc.so.6
#1  0x00007f8bf434e381 in abort () from /lib64/libc.so.6
#2  0x0000000000594d3a in OsAbort ()
#3  0x0000000000599f03 in AbortServer ()
#4  0x000000000059ad25 in FatalError ()
#5  0x00000000004233ad in xwl_read_events ()
#6  0x00000000005928b1 in ospoll_wait ()
#7  0x000000000058c0bb in WaitForSomething ()
#8  0x0000000000557ed3 in Dispatch ()
#9  0x000000000055c170 in dix_main ()
#10 0x00007f8bf433600a in __libc_start_main () from /lib64/libc.so.6
#11 0x0000000000422a9a in _start ()
(gdb)

Comment 14 Daniel Stone 2018-01-31 12:07:48 UTC
> 4:49:05 systemd-coredum: Process 6463 (gnome-shell) of user 1000 dumped core.
> 
> Stack trace of thread 6463:
> #0  0x00007fef247df630 st_theme_node_reduce_border_radius (libst-1.0.so)
> #1  0x00007fef247e1d69 st_theme_node_paint_borders (libst-1.0.so)
> #2  0x00007fef247e45f9 st_theme_node_paint (libst-1.0.so)
> #3  0x00007fef247e7d70 st_widget_paint_background (libst-1.0.so)
> #4  0x00007fef247cee4a st_label_paint (libst-1.0.so)
> #5  0x00007fef25a1ba1c clutter_actor_continue_paint (libmutter-clutter-1.so)

> 14:49:02 kernel: gnome-shell[6463]: segfault at 80 ip 00007fef247df630 sp 00007ffe06c93018 error 4 in libst-1.0.so[7fef247af000+4d000]
> 14:49:02 gnome-shell: clutter_paint_volume_set_height: assertion 'height >= 0.0f' failed

Yep, this is pretty clear what's happening. GNOME Shell is crashing because of an internal error. Xwayland immediately aborts as a result: it is a client of GNOME Shell so dies when the shell does.

I can't set the title, but this should be retitled to exclude Xwayland.

Comment 15 rugk 2018-02-01 20:31:57 UTC
Okay, changed the title.

The question is only *why* does GNOME Shell crash? Is it some kind of driver issue? (I don't think so, could reproduce it on two devices.)

Also, can you link the retrace.fedoraproject.org trace to this issue?

Comment 16 rugk 2018-02-07 21:38:11 UTC
I think I actually found some better STR: 
So it **is reproducible** when I move a window **in the overview** (i.e. super key) from one screen to another. The crash is triggered at the end of the drag- and drop "process" when the window is at the correct position.

Comment 17 Ben Cotton 2018-11-27 16:15:00 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.

Comment 18 Ben Cotton 2018-11-30 20:55:12 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.

Comment 19 Red Hat Bugzilla 2023-09-14 04:12:21 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.