Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1292832 - [abrt] devassistant-gui: display_handle_error(): python3.4 killed by SIGSEGV
Summary: [abrt] devassistant-gui: display_handle_error(): python3.4 killed by SIGSEGV
Alias: None
Product: Fedora
Classification: Fedora
Component: devassistant
Version: 25
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Bohuslav "Slavek" Kabrda
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:8993aac1ea5eefb86f031d4a9cf...
: 1351586 (view as bug list)
Depends On:
Blocks: WaylandRelated
TreeView+ depends on / blocked
Reported: 2015-12-18 13:10 UTC by Christian Stadelmann
Modified: 2016-11-24 16:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-11-24 16:41:51 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: core_backtrace (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: dso_list (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: exploitable (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: limits (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: maps (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: namespaces (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: open_fds (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details
File: proc_pid_status (deleted)
2015-12-18 13:10 UTC, Christian Stadelmann
no flags Details

System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 770906 0 None None None Never

Description Christian Stadelmann 2015-12-18 13:10:09 UTC
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:

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/python3 /usr/bin/da-gui
crash_function: display_handle_error
executable:     /usr/bin/python3.4
kernel:         4.2.7-300.fc23.x86_64
runlevel:       N 5
type:           CCpp

Truncated backtrace:
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

Comment 1 Christian Stadelmann 2015-12-18 13:10:15 UTC
Created attachment 1107145 [details]
File: backtrace

Comment 2 Christian Stadelmann 2015-12-18 13:10:17 UTC
Created attachment 1107146 [details]
File: core_backtrace

Comment 3 Christian Stadelmann 2015-12-18 13:10:18 UTC
Created attachment 1107147 [details]
File: dso_list

Comment 4 Christian Stadelmann 2015-12-18 13:10:20 UTC
Created attachment 1107148 [details]
File: exploitable

Comment 5 Christian Stadelmann 2015-12-18 13:10:21 UTC
Created attachment 1107149 [details]
File: limits

Comment 6 Christian Stadelmann 2015-12-18 13:10:23 UTC
Created attachment 1107150 [details]
File: maps

Comment 7 Christian Stadelmann 2015-12-18 13:10:25 UTC
Created attachment 1107151 [details]
File: namespaces

Comment 8 Christian Stadelmann 2015-12-18 13:10:26 UTC
Created attachment 1107152 [details]
File: open_fds

Comment 9 Christian Stadelmann 2015-12-18 13:10:28 UTC
Created attachment 1107153 [details]
File: proc_pid_status

Comment 10 arnaldo 2016-06-30 11:47:36 UTC
*** Bug 1351586 has been marked as a duplicate of this bug. ***

Comment 11 Olivier Fourdan 2016-09-01 07:26:59 UTC
WAYLAND_DEBUG to the rescue, shows the app gets killed because of a Wayland protocol error:

[528761.079] wl_display(xdg_shell@13, 2, "destroyed popup not top most popup")

Comment 12 Olivier Fourdan 2016-09-01 12:24:48 UTC
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.

Comment 13 Olivier Fourdan 2016-09-12 08:07:17 UTC
A fix for this has been pushed upstream in gtk+

Comment 14 Christian Stadelmann 2016-09-26 18:57:18 UTC
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

Comment 15 Fedora End Of Life 2016-11-24 14:20:15 UTC
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'
of '23'.

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.

Note You need to log in before you can comment on or make changes to this bug.