Description of problem: gnome-shell aquired an annoying habit of getting into what looks like an infinite loop of the following kind: ....... gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed gnome-shell[17514]: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed gnome-shell[17514]: g_object_set: assertion 'G_IS_OBJECT (object)' failed ...... This may have the following outcomes: - a computer locks up and requires powering down to recover - sometimes, and after a while, the whole session restarts by itself and dumps you to a login screen - on rare occasions a core is dumped and a rather big one; about 370 MB of an lz4 compressed image and 2GB uncompressed. Attempts to check such core with gdb give only something of that kind: BFD: Warning: /var/lib/systemd/coredump/core is truncated: expected core file size >= 2940010496, found: 2147483648. [New LWP 1405] ..... Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f180a211510 in ?? () [Current thread is 1 (LWP 1405)] (gdb) where #0 0x00007f180a211510 in ?? () Backtrace stopped: Cannot access memory at address 0x7fff8472f778 Version-Release number of selected component (if applicable): gnome-shell-3.22.3-1.fc25.x86_64 How reproducible: No idea how to trigger. It seems that attempts to use a file selector in evince are somewhat likely to trigger that behaviour but this neither given nor necessary. OTOH it is becoming quite annoying. Additional info: It is quite possible, or even likely, that bugs elsewhere trigger that behaviour but it is gnome-shell that eventually seriously misbehaves.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.