Description of problem: I run dconf-editor and gnome crashed Version-Release number of selected component: gnome-shell-3.13.4-3.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: x_io_error executable: /usr/bin/gnome-shell kernel: 3.17.0-0.rc0.git7.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 x_io_error at /lib64/libmutter.so.0 #3 _XIOError at /lib64/libX11.so.6 #4 _XReply at /lib64/libX11.so.6 #5 _XGetWindowAttributes at /lib64/libX11.so.6 #6 XGetWindowAttributes at /lib64/libX11.so.6 #7 meta_window_x11_new at /lib64/libmutter.so.0 #8 handle_other_xevent at /lib64/libmutter.so.0 #9 xevent_filter at /lib64/libmutter.so.0 #10 gdk_event_apply_filters at /lib64/libgdk-3.so.0 #11 _gdk_x11_display_queue_events at /lib64/libgdk-3.so.0
Created attachment 928002 [details] File: backtrace
Created attachment 928003 [details] File: cgroup
Created attachment 928004 [details] File: core_backtrace
Created attachment 928005 [details] File: dso_list
Created attachment 928006 [details] File: environ
Created attachment 928007 [details] File: limits
Created attachment 928008 [details] File: maps
Created attachment 928009 [details] File: open_fds
Created attachment 928010 [details] File: proc_pid_status
Created attachment 928011 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Probably a duplicate of #1065109
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.