Description of problem: Running clear Version-Release number of selected component: gnome-terminal-3.16.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: g_assertion_message_cmpnum executable: /usr/libexec/gnome-terminal-server global_pid: 2834 kernel: 4.0.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at So 2015-04-26 14:32:04 CEST, end at So 2015-04-26 14:36:35 CEST. -- Truncated backtrace: Thread no. 1 (10 frames) #3 g_assertion_message_cmpnum at gtestutils.c:2404 #4 _vte_boa_reset at vtestream-file.h:851 #5 _vte_file_stream_reset at vtestream-file.h:1083 #6 _vte_ring_reset_streams at ring.c:324 #7 _vte_ring_drop_scrollback at ring.c:637 #8 _vte_terminal_drop_scrollback at vte.c:3026 #9 vte_sequence_handler_erase_in_display at vteseq.c:2597 #10 vte_terminal_process_incoming at vte.c:3827 #11 time_process_incoming at vte.c:12621 #12 update_timeout at vte.c:12914
Created attachment 1018992 [details] File: backtrace
Created attachment 1018993 [details] File: cgroup
Created attachment 1018994 [details] File: core_backtrace
Created attachment 1018995 [details] File: dso_list
Created attachment 1018996 [details] File: environ
Created attachment 1018997 [details] File: limits
Created attachment 1018998 [details] File: maps
Created attachment 1018999 [details] File: mountinfo
Created attachment 1019000 [details] File: namespaces
Created attachment 1019001 [details] File: open_fds
Created attachment 1019002 [details] File: proc_pid_status
Upstream: https://bugzilla.gnome.org/show_bug.cgi?id=748484
vte 0.40.2 is believed to fix this problem.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.