Red Hat Bugzilla – Bug 1292832
[abrt] devassistant-gui: display_handle_error(): python3.4 killed by SIGSEGV
Last modified: 2016-11-24 11:41:51 EST
Description of problem:
Steps to reproduce:
1. run a gnome+wayland session
2. open devassistant-gui
3. select python, than click on "gtk3" in popup menu
devassistant immediately crashes.
This issue is not present when using CLI or running devassistant-gui inside XWayland (with GDK_BACKEND=x11).
Version-Release number of selected component:
cmdline: /usr/bin/python3 /usr/bin/da-gui
runlevel: N 5
Thread no. 1 (10 frames)
#0 display_handle_error at src/wayland-client.c:716
#1 ffi_call_unix64 at ../src/x86/unix64.S:76
#2 ffi_call at ../src/x86/ffi64.c:525
#3 wl_closure_invoke at src/connection.c:945
#4 dispatch_event at src/wayland-client.c:1173
#5 dispatch_queue at src/wayland-client.c:1341
#6 wl_display_dispatch_queue at src/wayland-client.c:1587
#7 wl_display_roundtrip_queue at src/wayland-client.c:987
#8 gtk_menu_shell_activate_item at gtkmenushell.c:1373
#9 gtk_menu_shell_button_release at gtkmenushell.c:788
Created attachment 1107145 [details]
Created attachment 1107146 [details]
Created attachment 1107147 [details]
Created attachment 1107148 [details]
Created attachment 1107149 [details]
Created attachment 1107150 [details]
Created attachment 1107151 [details]
Created attachment 1107152 [details]
Created attachment 1107153 [details]
*** Bug 1351586 has been marked as a duplicate of this bug. ***
WAYLAND_DEBUG to the rescue, shows the app gets killed because of a Wayland protocol error:
[528761.079] firstname.lastname@example.org(xdg_shell@13, 2, "destroyed popup not top most popup")
Seems like devassistant-gui is umapping its toplevel window while the popup are still present, causing handle_popup_parent_destroyed() to be reached in mutter which will rightfully send back an error to the client, which kills it...
While this is no problem in X11, xsg-shell on Wayland won't allow that - So I am trying to see if we could avoid that at the gtk+ level, when an app does that, otherwise the fix would belong to the app.
A fix for this has been pushed upstream in gtk+
The crasher is gone, thanks!
Now the window is putting itself into background, which looks pretty weird. The window still has focus, but is not displayed topmost. Instead an inactive (insensitive) window is printed in front of devassistant-gui
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.