Version-Release number of selected component: gnome-terminal-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: g_datalist_id_dup_data executable: /usr/libexec/gnome-terminal-server global_pid: 2541 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_datalist_id_dup_data at gdataset.c:858 #1 g_datalist_id_get_data at gdataset.c:798 #2 toggle_refs_notify at gobject.c:2886 #3 g_hash_table_remove_all_nodes at ghash.c:548 #5 g_hash_table_remove_all at ghash.c:1428 #6 g_hash_table_destroy at ghash.c:1122 #7 g_datalist_clear at gdataset.c:273 #9 g_value_unset at gvalue.c:272 #12 gtk_css_node_set_style at gtkcssnode.c:867 #13 gtk_css_node_ensure_style at gtkcssnode.c:928
Created attachment 1095939 [details] File: backtrace
Created attachment 1095940 [details] File: cgroup
Created attachment 1095941 [details] File: core_backtrace
Created attachment 1095942 [details] File: dso_list
Created attachment 1095943 [details] File: environ
Created attachment 1095944 [details] File: exploitable
Created attachment 1095945 [details] File: limits
Created attachment 1095946 [details] File: maps
Created attachment 1095947 [details] File: mountinfo
Created attachment 1095948 [details] File: open_fds
Created attachment 1095949 [details] File: proc_pid_status
*** Bug 1310459 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: As near as I can determine, pressed the up-arrow key a few times reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: g_datalist_id_dup_data executable: /usr/libexec/gnome-terminal-server global_pid: 2769 kernel: 4.3.3-303.fc23.x86_64 package: gnome-terminal-3.18.2-1.fc23 reason: gnome-terminal-server killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Watching a video with mplayer. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: g_datalist_id_dup_data executable: /usr/libexec/gnome-terminal-server global_pid: 9518 kernel: 4.3.3-303.fc23.x86_64 package: gnome-terminal-3.18.2-1.fc23 reason: gnome-terminal-server killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
I've hit this twice in one day now. Surely this must make this bug important enough to at least triage, yes?
*** Bug 1344844 has been marked as a duplicate of this bug. ***
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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.