Created attachment 1367891 [details] journalctl /usr/bin/gnome-shell output excerpt Description of problem: I've seen this a couple of times the last couple of days. It appears when I start firefox (has decorations enabled as described here[1]) and have hexchat and evolution already running gnome-shell seems to crash on me. [1] https://fedoramagazine.org/firefox-quantum-look-native-f27/ Version-Release number of selected component (if applicable): $ rpm -q gnome-shell evolution firefox gnome-shell-3.26.2-1.fc27.x86_64 evolution-3.26.2-1.fc27.x86_64 firefox-57.0.1-1.fc27.x86_64 How reproducible: Pretty consistent (80%?), but not entirely sure what the sufficient steps are. Steps to Reproduce: 1. Start hexchat and evolution. 2. Start Firefox. Actual results: Gnome shell crashes (goes back to the login screen). Firefox, hexchat and evolution die with it. Expected results: No crash. Additional info: This stack-trace seems to show up in journalctl when the crash happens: Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: == Stack trace for context 0x5633300f3000 == Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #0 0x7ffc18b24e90 b resource:///org/gnome/shell/ui/panel.js:199 (0x7f8c21e06b38 @ 88) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #1 0x7ffc18b24ef0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8c384c2bc0 @ 71) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #2 0x7ffc18b24fa0 b resource:///org/gnome/shell/ui/panel.js:330 (0x7f8c21e08098 @ 804) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #3 0x7ffc18b25000 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8c384c2bc0 @ 71) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #4 0x7ffc18b250a0 b resource:///org/gnome/shell/ui/panel.js:254 (0x7f8c21e06de0 @ 156) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #5 0x7ffc18b25110 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8c384c2bc0 @ 71) Dec 13 10:09:59 unknown54EE7535D1D4 org.gnome.Shell.desktop[1965]: #6 0x7ffc18b25160 I self-hosted:917 (0x7f8c384ee5e8 @ 394) If I start firefox first and then other programs it tends to not crash.
Maybe it's worth noting that I use multiple (2) external monitors.
It just happened again. This time with only starting firefox. Abrt pointed out this retrace url: https://retrace.fedoraproject.org/faf/reports/1999013/ Thus, reassigning to xorg-x11-server which provides Xwayland. $ rpm -qf /usr/bin/Xwayland xorg-x11-server-Xwayland-1.19.6-1.fc27.x86_64 $ rpm -q firefox firefox-57.0.4-1.fc27.x86_64
The snippet from "journalctl /usr/bin/gnome-shell" from today looks like this: Jan 11 09:37:52 localhost.localdomain org.gnome.Shell.desktop[1241]: glamor: EGL version 1.4 (DRI2): Jan 11 09:37:53 localhost.localdomain gnome-shell[1241]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Jan 11 09:37:53 localhost.localdomain gnome-shell[1241]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Jan 11 09:37:53 localhost.localdomain gnome-shell[1241]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" Jan 11 09:37:53 localhost.localdomain gnome-shell[1241]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Jan 11 09:37:54 localhost.localdomain gnome-shell[1241]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jan 11 09:37:54 localhost.localdomain gnome-shell[1241]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1471]: reference to undefined property "MetaWindowX11" Jan 11 09:38:09 localhost.localdomain org.gnome.Shell.desktop[1957]: glamor: EGL version 1.4 (DRI2): Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: Unable to connect to ibus: Could not connect: Connection refused Jan 11 09:38:10 localhost.localdomain gnome-shell[1957]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jan 11 09:38:20 localhost.localdomain gnome-shell[1957]: STACK_OP_ADD: window 0x1c00001 already in stack Jan 11 09:38:20 localhost.localdomain gnome-shell[1957]: STACK_OP_ADD: window 0x1c00001 already in stack Jan 11 09:38:21 localhost.localdomain gnome-shell[1957]: GNOME Shell started at Thu Jan 11 2018 09:38:10 GMT+0100 (CET) Jan 11 09:38:50 localhost.localdomain gnome-shell[1957]: JS WARNING: [resource:///org/gnome/shell/ui/modalDialog.js 218]: reference to undefined property "GdkX11Screen" Jan 11 09:38:51 localhost.localdomain gnome-shell[1957]: The property brightness doesn't seem to be a normal object property of [0x55e3db60cd80 StWidget] or a registered special property Jan 11 09:38:51 localhost.localdomain gnome-shell[1957]: The property vignette_sharpness doesn't seem to be a normal object property of [0x55e3db60cd80 StWidget] or a registered special property Jan 11 09:38:51 localhost.localdomain gnome-shell[1957]: The property brightness doesn't seem to be a normal object property of [0x55e3db629840 StWidget] or a registered special property Jan 11 09:38:51 localhost.localdomain gnome-shell[1957]: The property vignette_sharpness doesn't seem to be a normal object property of [0x55e3db629840 StWidget] or a registered special property Jan 11 09:39:11 localhost.localdomain gnome-shell[1957]: Invalid result meta returned from search provider seahorse.desktop Jan 11 09:39:15 localhost.localdomain gnome-shell[1957]: gmem.c:130: failed to allocate 18446744072098939136 bytes Jan 11 09:39:15 localhost.localdomain audit[1957]: ANOM_ABEND auid=15263 uid=15263 gid=15263 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1957 comm="gnome-shell" exe="/usr/bin/gnome-shell Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: == Stack trace for context 0x55e3d91b1000 == Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #0 0x7ffd796bfa10 b resource:///org/gnome/shell/ui/panel.js:199 (0x7ff32d106b38 @ 88) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #1 0x7ffd796bfa70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #2 0x7ffd796bfb20 b resource:///org/gnome/shell/ui/panel.js:330 (0x7ff32d109098 @ 804) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #3 0x7ffd796bfb80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #4 0x7ffd796c0300 b resource:///org/gnome/shell/ui/panel.js:254 (0x7ff32d106de0 @ 156) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #5 0x7ffd796c0a40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) Jan 11 09:39:15 localhost.localdomain org.gnome.Shell.desktop[1957]: #6 0x7ffd796c0a90 I self-hosted:917 (0x7ff32ddee5e8 @ 394) Jan 11 09:39:30 localhost.localdomain org.gnome.Shell.desktop[4401]: glamor: EGL version 1.4 (DRI2): Jan 11 09:39:31 localhost.localdomain gnome-shell[4401]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Jan 11 09:39:31 localhost.localdomain gnome-shell[4401]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Jan 11 09:39:31 localhost.localdomain gnome-shell[4401]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" Jan 11 09:39:31 localhost.localdomain gnome-shell[4401]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Jan 11 09:39:31 localhost.localdomain gnome-shell[4401]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Jan 11 09:39:41 localhost.localdomain gnome-shell[4401]: STACK_OP_ADD: window 0x1a00001 already in stack Jan 11 09:39:41 localhost.localdomain gnome-shell[4401]: STACK_OP_ADD: window 0x1a00001 already in stack Jan 11 09:39:42 localhost.localdomain gnome-shell[4401]: GNOME Shell started at Thu Jan 11 2018 09:39:31 GMT+0100 (CET) Jan 11 09:39:53 localhost.localdomain gnome-shell[4401]: The property brightness doesn't seem to be a normal object property of [0x558bff01d7a0 StWidget] or a registered special property Jan 11 09:39:53 localhost.localdomain gnome-shell[4401]: The property vignette_sharpness doesn't seem to be a normal object property of [0x558bff01d7a0 StWidget] or a registered special property Jan 11 09:39:53 localhost.localdomain gnome-shell[4401]: The property brightness doesn't seem to be a normal object property of [0x558bff018440 StWidget] or a registered special property Jan 11 09:39:53 localhost.localdomain gnome-shell[4401]: The property vignette_sharpness doesn't seem to be a normal object property of [0x558bff018440 StWidget] or a registered special property Jan 11 09:48:27 localhost.localdomain gnome-shell[4401]: The property brightness doesn't seem to be a normal object property of [0x558bff84cc50 StWidget] or a registered special property Jan 11 09:48:27 localhost.localdomain gnome-shell[4401]: The property vignette_sharpness doesn't seem to be a normal object property of [0x558bff84cc50 StWidget] or a registered special property Jan 11 09:48:27 localhost.localdomain gnome-shell[4401]: The property brightness doesn't seem to be a normal object property of [0x558bff87f6f0 StWidget] or a registered special property Jan 11 09:48:27 localhost.localdomain gnome-shell[4401]: The property vignette_sharpness doesn't seem to be a normal object property of [0x558bff87f6f0 StWidget] or a registered special property Jan 11 09:48:55 localhost.localdomain gnome-shell[4401]: Received error from DBus search provider org.gnome.Calendar.desktop: Gio.IOErrorEnum: Timeout was reached That's a boot => start gnome session => attempt to start firefox => gnome-shell crashes => auto-restart of gnome-shell.
I don't see any indication of Xwayland crashing in any of the data provided, but I do see a backtrace of gnome-shell in Javascript. in comment 3, you mention that gnome-shell crashes and auto-restart, this is not possible on Wayland (unfortunately) so that would mean you're running GNOME on Xorg instead. Are you sure you're running GNOME on Wayland? (see https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Identifying_the_session_type_in_runtime_)
(In reply to Olivier Fourdan from comment #4) > I don't see any indication of Xwayland crashing in any of the data provided, > but I do see a backtrace of gnome-shell in Javascript. Right. That was abrt doing it's thing. It claimed xorg-x11-server crashed with a reference to the retrace URL as listed in comment 2. > in comment 3, you mention that gnome-shell crashes and auto-restart, this is > not possible on Wayland (unfortunately) so that would mean you're running > GNOME on Xorg instead. Interesting. By auto-restart I meant I get back to the login screen. So all open windows were lost. IIRC, old gnome-shell restarts on X preserved windows. Maybe that's were the confusion comes from? Should gnome-shell not restart at all on wayland and not-even present the login screen? > Are you sure you're running GNOME on Wayland? (see > https://fedoraproject.org/wiki/ > How_to_debug_Wayland_problems#Identifying_the_session_type_in_runtime_) Looks like it's Wayland. $ echo $WAYLAND_DISPLAY wayland-0 $ loginctl SESSION UID USER SEAT TTY c1 42 gdm seat0 /dev/tty1 4 15263 sgehwolf seat0 /dev/tty2 2 sessions listed. $ loginctl show-session 4 -p Type Type=wayland
Ok, good, got confused by "auto-restart". Yet, as wrote in comment 4, it doesn't look like Xwayland is crashing there, based on the data provided in comment 3: gnome-shell[1957]: gmem.c:130: failed to allocate 18446744072098939136 bytes org.gnome.Shell.desktop[1957]: == Stack trace for context 0x55e3d91b1000 == org.gnome.Shell.desktop[1957]: #0 0x7ffd796bfa10 b resource:///org/gnome/shell/ui/panel.js:199 (0x7ff32d106b38 @ 88) org.gnome.Shell.desktop[1957]: #1 0x7ffd796bfa70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) org.gnome.Shell.desktop[1957]: #2 0x7ffd796bfb20 b resource:///org/gnome/shell/ui/panel.js:330 (0x7ff32d109098 @ 804) org.gnome.Shell.desktop[1957]: #3 0x7ffd796bfb80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) org.gnome.Shell.desktop[1957]: #4 0x7ffd796c0300 b resource:///org/gnome/shell/ui/panel.js:254 (0x7ff32d106de0 @ 156) org.gnome.Shell.desktop[1957]: #5 0x7ffd796c0a40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) org.gnome.Shell.desktop[1957]: #6 0x7ffd796c0a90 I self-hosted:917 (0x7ff32ddee5e8 @ 394) - So what makes you think this is Xwayland crashing? - Can you provide a stacktrace of Xwayland at the time of the crash? (You can use “coredumpctl list” and “coredumpctl gdb <id>” and issue a “bt”) Note: Reason I insist here is because recent changes in mutter make any gnome-shell crash abort Xwayland, which make it look like Xwayland crashes while it's actually the Wayland compositor (gnome-shell/mutter) crashing.
(In reply to Olivier Fourdan from comment #6) > Ok, good, got confused by "auto-restart". OK. > Yet, as wrote in comment 4, it doesn't look like Xwayland is crashing there, > based on the data provided in comment 3: > > gnome-shell[1957]: gmem.c:130: failed to allocate 18446744072098939136 bytes > org.gnome.Shell.desktop[1957]: == Stack trace for context 0x55e3d91b1000 == > org.gnome.Shell.desktop[1957]: #0 0x7ffd796bfa10 b > resource:///org/gnome/shell/ui/panel.js:199 (0x7ff32d106b38 @ 88) > org.gnome.Shell.desktop[1957]: #1 0x7ffd796bfa70 I > resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) > org.gnome.Shell.desktop[1957]: #2 0x7ffd796bfb20 b > resource:///org/gnome/shell/ui/panel.js:330 (0x7ff32d109098 @ 804) > org.gnome.Shell.desktop[1957]: #3 0x7ffd796bfb80 I > resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) > org.gnome.Shell.desktop[1957]: #4 0x7ffd796c0300 b > resource:///org/gnome/shell/ui/panel.js:254 (0x7ff32d106de0 @ 156) > org.gnome.Shell.desktop[1957]: #5 0x7ffd796c0a40 I > resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff32ddc2bc0 @ 71) > org.gnome.Shell.desktop[1957]: #6 0x7ffd796c0a90 I self-hosted:917 > (0x7ff32ddee5e8 @ 394) > > - So what makes you think this is Xwayland crashing? Like I said earlier. That's what abrt thought. If abrt is wrong, feel free to re-assign. > - Can you provide a stacktrace of Xwayland at the time of the crash? > (You can use “coredumpctl list” and “coredumpctl gdb <id>” and issue a > “bt”) > > Note: Reason I insist here is because recent changes in mutter make any > gnome-shell crash abort Xwayland, which make it look like Xwayland crashes > while it's actually the Wayland compositor (gnome-shell/mutter) crashing. I'm attaching stack traces of Xwayland and gnome-shell as determined by: $ sudo coredumpctl info --since 2018-01-11 /usr/bin/{gnome-shell,Xwayland} Then feel free to take a look and re-assign as appropriate. I don't know if this is an Xwayland issue or gnome-shell/mutter issue. You are in a much better position to determine that. Note that the crash happened at 09:39 CET. So the times of the Xwayland and gnome-shell crashes match up. Though, the timestamp of the gnome-shell crash seems one second earlier (Thu 2018-01-11 09:39:15 CET vs Thu 2018-01-11 09:39:16 CET), which seems to suggest it originated there and brought down Xwayland as well.
Created attachment 1379933 [details] gnome-shell backtrace at time of crash.
Created attachment 1379934 [details] Xwayland backtrace at time of crash
Ok, many thanks! This from attachment 1379934 [details] : #2 0x0000000000594d3a OsAbort (Xwayland) #3 0x0000000000599f03 AbortServer (Xwayland) #4 0x000000000059ad25 FatalError (Xwayland) #5 0x00000000004233ad xwl_read_events (Xwayland) is typical of what I was saying, basically, Xwayland is telling that the otehr side of the Wayland socket (ie gnome-shell/mutter) is gone. This is not an Xwayland crash. → moving the bug back to gnome-shell.
And for the record, I suspect this (from attachment 1379933 [details]): #8 0x00007ff37ac1b424 g_malloc0 (libglib-2.0.so.0) #9 0x00007ff3786494e0 blur_pixels (libst-1.0.so) #10 0x00007ff378649cbe _st_create_shadow_pipeline (libst-1.0.so) #11 0x00007ff37864a0ab _st_create_shadow_pipeline_from_actor (libst-1.0.so) is what is causing this message in the logs (from attachment 1367891 [details]): gnome-shell[1957]: gmem.c:130: failed to allocate 18446744072098939136 bytes Could you capture a full backtrace with the debuginfo installed?
Created attachment 1379943 [details] gnome-shell backtrace at time of crash with gnome-shell/mutter debuginfo installed.
Created attachment 1379945 [details] gnome-shell backtrace at time of crash with gnome-shell/mutter debuginfo installed.
This happened again today. Different hardware by now. Laptop Lenovo P50, gnome-shell under X. I'm attaching the output of $ journalctl --since 2018-01-31 /usr/bin/gnome-shell Note this line: Jan 31 09:27:27 p50-laptop gnome-shell[1953]: gmem.c:130: failed to allocate 18446744072098939136 bytes
Created attachment 1388824 [details] journalctl --since 2018-01-31 /usr/bin/gnome-shell There seems to be no usable backtrace.
Out of curiosity, can you reproduce with all g-s extensions disabled?
Possible fix proposed here: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/3
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.
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.