Version-Release number of selected component: gnome-terminal-3.32.1-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: gtk_widget_hide executable: /usr/libexec/gnome-terminal-server journald_cursor: s=e251080213eb4c539c11989e8791d4a9;i=862aeb;b=7aa3120876f1499e8a96bc0796eee74b;m=4a9ac4d4f4;t=587b8c2a5b235;x=677ee1b8fb1e5ede kernel: 5.0.8-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 8086 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_hide at gtkwidget.c:4878 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:525 #3 g_cclosure_marshal_generic at ../gobject/gclosure.c:1500 #8 g_menu_model_items_changed at ../gio/gmenumodel.c:690 #9 g_menu_remove_all at ../gio/gmenu.c:510 #10 terminal_app_update_profile_menus at terminal-app.c:570 #15 g_settings_real_change_event at ../gio/gsettings.c:391 #16 ffi_call_unix64 at ../src/x86/unix64.S:76 #17 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1560163 [details] File: backtrace
Created attachment 1560164 [details] File: cgroup
Created attachment 1560165 [details] File: core_backtrace
Created attachment 1560166 [details] File: cpuinfo
Created attachment 1560167 [details] File: dso_list
Created attachment 1560168 [details] File: environ
Created attachment 1560169 [details] File: exploitable
Created attachment 1560170 [details] File: limits
Created attachment 1560171 [details] File: maps
Created attachment 1560172 [details] File: mountinfo
Created attachment 1560173 [details] File: open_fds
Created attachment 1560174 [details] File: proc_pid_status
Looks like a crash inside gtk+'s menu code while updating the profile section of the headerbar menu when one of the profile's 'visible-name' key changed. I couldn't reproduce this here. Any additional information about what you were doing at the time? Are there any assertion failed messages from gnome-terminal-server in the journal?
Reproduced while running gnome-terminal-server under valgrind and adding a new profile with same backtrace under terminal_app_update_profile_menus().
Fixed upstream on master and 3-32 branch.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.