Hide Forgot
Version-Release number of selected component: gnome-shell-3.19.3-1.fc24 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell global_pid: 2190 kernel: 4.4.0-0.rc8.git3.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4033 #1 g_object_ref at gobject.c:3049 #2 g_hash_table_foreach at ghash.c:1608 #3 spi_cache_foreach at accessible-cache.c:417 #4 impl_GetItems at cache-adaptor.c:286 #5 handle_other at droute.c:553 #6 handle_message at droute.c:600 #7 _dbus_object_tree_dispatch_and_unlock at ../../dbus/dbus-object-tree.c:1020 #9 message_queue_dispatch at atspi-gmain.c:89 #14 meta_run at core/main.c:521 Potential duplicate: bug 1296273
Created attachment 1114074 [details] File: backtrace
Created attachment 1114075 [details] File: cgroup
Created attachment 1114076 [details] File: core_backtrace
Created attachment 1114077 [details] File: dso_list
Created attachment 1114078 [details] File: environ
Created attachment 1114079 [details] File: exploitable
Created attachment 1114080 [details] File: limits
Created attachment 1114081 [details] File: maps
Created attachment 1114082 [details] File: mountinfo
Created attachment 1114083 [details] File: namespaces
Created attachment 1114084 [details] File: open_fds
Created attachment 1114085 [details] File: proc_pid_status
Created attachment 1114086 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Similar problem has been detected: My computer has a touchscreen (Gnome seldom have problems with it)- It's Lenovo YOGA 500. This time, a touched the screen to try scrolling an pdf file in evince, but it didn't work. So, I used my mouse (wireless one-Logitech).After that, the Gnome Shell restarted. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell global_pid: 1931 kernel: 4.7.4-200.fc24.x86_64 package: gnome-shell-3.20.4-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.