Version-Release number of selected component: control-center-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: XQueryExtension executable: /usr/bin/gnome-control-center global_pid: 21407 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Sun 2014-11-09 04:43:19 IST, end at Mon 2015-05-25 18:27:48 IST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 XQueryExtension at QuExt.c:43 #1 _XiFindEventsSupported at XExtInt.c:171 #2 XInput_find_display at XExtInt.c:221 #3 XListInputDevices at XListDev.c:184 #4 gsd_wacom_device_constructor at gsd-wacom-device.c:1439 #5 g_object_new_with_custom_constructor at gobject.c:1692 #6 g_object_new_internal at gobject.c:1772 #7 g_object_new_valist at gobject.c:2033 #9 gsd_wacom_device_new at gsd-wacom-device.c:1653 #10 add_known_device at cc-wacom-panel.c:365
Created attachment 1029440 [details] File: backtrace
Created attachment 1029441 [details] File: cgroup
Created attachment 1029442 [details] File: core_backtrace
Created attachment 1029443 [details] File: dso_list
Created attachment 1029444 [details] File: environ
Created attachment 1029445 [details] File: limits
Created attachment 1029446 [details] File: maps
Created attachment 1029447 [details] File: mountinfo
Created attachment 1029448 [details] File: namespaces
Created attachment 1029449 [details] File: open_fds
Created attachment 1029451 [details] File: proc_pid_status
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.