Description of problem: It crashes whenever launched when running in Wayland. Version-Release number of selected component: gnome-nibbles-3.16.1-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: gnome-nibbles crash_function: clutter_gdk_get_visual executable: /usr/bin/gnome-nibbles global_pid: 4755 kernel: 4.1.5-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 clutter_gdk_get_visual at gdk/clutter-backend-gdk.c:538 #2 gtk_clutter_embed_realize at ./gtk-clutter-embed.c:359 #3 _g_closure_invoke_va at gclosure.c:831 #6 gtk_widget_realize at gtkwidget.c:5525 #7 gtk_widget_map at gtkwidget.c:5052 #8 gtk_container_map at gtkcontainer.c:3563 #9 _g_closure_invoke_va at gclosure.c:831 #12 gtk_widget_map at gtkwidget.c:5054 #13 gtk_box_forall at gtkbox.c:2558 #14 gtk_container_map at gtkcontainer.c:3563
Created attachment 1066369 [details] File: backtrace
Created attachment 1066370 [details] File: cgroup
Created attachment 1066371 [details] File: core_backtrace
Created attachment 1066372 [details] File: dso_list
Created attachment 1066373 [details] File: environ
Created attachment 1066374 [details] File: limits
Created attachment 1066375 [details] File: maps
Created attachment 1066376 [details] File: mountinfo
Created attachment 1066377 [details] File: namespaces
Created attachment 1066378 [details] File: open_fds
Created attachment 1066379 [details] File: proc_pid_status
Created attachment 1066380 [details] File: var_log_messages
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.