Description of problem: activated destkop sharing and logged in to gnome@wayland Version-Release number of selected component: vino-3.15.4-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/vino-server crash_function: XQueryExtension executable: /usr/libexec/vino-server kernel: 3.19.0-0.rc6.git3.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 XQueryExtension at QuExt.c:43 #1 get_xinput_base at XTest.c:79 #2 find_display at XTest.c:83 #3 XTestQueryExtension at XTest.c:101 #4 vino_input_init at server/vino-input.c:761 #5 name_acquired at server/vino-main.c:152 #6 do_call at gdbusnameowning.c:215 #7 request_name_cb at gdbusnameowning.c:327 #8 g_simple_async_result_complete at gsimpleasyncresult.c:763 #9 g_dbus_connection_call_done at gdbusconnection.c:5508
Created attachment 987027 [details] File: backtrace
Created attachment 987028 [details] File: cgroup
Created attachment 987029 [details] File: core_backtrace
Created attachment 987030 [details] File: dso_list
Created attachment 987031 [details] File: environ
Created attachment 987032 [details] File: exploitable
Created attachment 987033 [details] File: limits
Created attachment 987034 [details] File: maps
Created attachment 987035 [details] File: open_fds
Created attachment 987036 [details] File: proc_pid_status
Created attachment 987037 [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
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.