Description of problem: running empathy within Gnome on Wayland Version-Release number of selected component: empathy-3.12.11-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: _XInternAtom executable: /usr/libexec/empathy-chat global_pid: 6304 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _XInternAtom at IntAtom.c:85 #1 XInternAtom at IntAtom.c:175 #2 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:115 #3 window_get_workspace at empathy-ui-utils.c:1209 #4 empathy_move_to_window_desktop at empathy-ui-utils.c:1231 #5 empathy_chat_window_present_chat at empathy-chat-window.c:2862 #6 process_tp_chat at empathy-chat-manager.c:224 #7 handle_channels at empathy-chat-manager.c:270 #9 handle_channels_context_prepare_cb at base-client.c:2384 #10 g_simple_async_result_complete at gsimpleasyncresult.c:801
Created attachment 1084832 [details] File: backtrace
Created attachment 1084833 [details] File: cgroup
Created attachment 1084834 [details] File: core_backtrace
Created attachment 1084835 [details] File: dso_list
Created attachment 1084836 [details] File: environ
Created attachment 1084837 [details] File: exploitable
Created attachment 1084838 [details] File: limits
Created attachment 1084839 [details] File: maps
Created attachment 1084840 [details] File: mountinfo
Created attachment 1084841 [details] File: open_fds
Created attachment 1084842 [details] File: proc_pid_status
Created attachment 1084843 [details] File: var_log_messages
Another user experienced a similar problem: Trying to open a conversation reported a crash. Note: using Wayland. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/empathy-chat crash_function: _XInternAtom executable: /usr/libexec/empathy-chat global_pid: 6101 kernel: 4.2.6-libre.300.fc23.gnu.x86_64 package: empathy-3.12.11-1.fc23 reason: empathy-chat killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** This bug has been marked as a duplicate of bug 1282614 ***