Description of problem:
I selected multiple slides in Impress and did right-click to get a context menu.
Version-Release number of selected component:
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reproducible: Not sure how to reproduce the problem
runlevel: N 5
Thread no. 1 (10 frames)
#0 wl_resource_post_error at src/wayland-server.c:217
#1 handle_popup_parent_destroyed at wayland/meta-wayland-surface.c:1610
#2 wl_signal_emit at src/wayland-server-core.h:330
#3 destroy_resource at src/wayland-server.c:567
#4 for_each_helper at src/wayland-util.c:359
#5 wl_map_for_each at src/wayland-util.c:365
#6 wl_client_destroy at src/wayland-server.c:709
#7 wl_client_connection_data at src/wayland-server.c:248
#8 wl_event_loop_dispatch at src/event-loop.c:421
#9 wayland_event_source_dispatch at wayland/meta-wayland.c:77
Created attachment 1150874 [details]
Created attachment 1150875 [details]
Created attachment 1150876 [details]
Created attachment 1150877 [details]
Created attachment 1150878 [details]
Created attachment 1150879 [details]
Created attachment 1150880 [details]
Created attachment 1150881 [details]
Created attachment 1150882 [details]
Created attachment 1150883 [details]
Created attachment 1150884 [details]
Created attachment 1150885 [details]
Created attachment 1150886 [details]
The erro looks the same as bug 1292832 (i.e. "destroyed popup not top most
popup") but here, sending the error also causs a segfault in gnome-shell...
I can reproduce this bug by trying to reproduce bug #1290784:
0. in a gnome+wayland session
1. open eclipse
2. in the perspective switcher (top right), right-click on any perspective.
See bug #1372311 for a backtrace on F25.
This one and bug #1372311 looks the same, and none of them reproduce. Should one be made a duplicate, and the other marked as fixed?
(In reply to Jonas Ådahl from comment #16)
> This one and bug #1372311 looks the same, and none of them reproduce. Should
> one be made a duplicate, and the other marked as fixed?
I think so. The other one is marked as fixed already, so this one can be closed I think.
*** This bug has been marked as a duplicate of bug 1372311 ***