Bug 1198258

Summary: [abrt] gnome-terminal: vte_terminal_accessible_get_text(): gnome-terminal-server killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Bruce-Robert Pocock <brpocock>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: egmont, mclasen, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1eec29047854da73c1205a367d2ea1aa30a2e11d
Whiteboard: abrt_hash:3a1c4e4414594ad2c47c9b36e3c65986787a7bf5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 09:40:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Bruce-Robert Pocock 2015-03-03 16:29:52 UTC 
Description of problem:
Possibly coïncidence, but all terminals crashed after closing one through confirming, “yes, it's OK if it's busy, close it anyway” dialog. 

Version-Release number of selected component:
gnome-terminal-3.14.2-2.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: vte_terminal_accessible_get_text
executable:     /usr/libexec/gnome-terminal-server
kernel:         3.18.7-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 vte_terminal_accessible_get_text at vteaccess.c:864
 #1 text_changed_event_listener at event.c:903
 #4 g_signal_emit_by_name at gsignal.c:3405
 #5 emit_text_changed_delete at vteaccess.c:197
 #7 vte_terminal_accessible_text_scrolled at vteaccess.c:602
 #8 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
 #9 _g_closure_invoke_va at gclosure.c:831
 #11 g_signal_emit_by_name at gsignal.c:3405
 #12 vte_terminal_handle_scroll at vte.c:986
 #17 gtk_adjustment_value_changed at gtkadjustment.c:894
Comment 1 Bruce-Robert Pocock 2015-03-03 16:29:54 UTC 
Created attachment 997579 [details]
File: backtrace
Comment 2 Bruce-Robert Pocock 2015-03-03 16:29:55 UTC 
Created attachment 997580 [details]
File: cgroup
Comment 3 Bruce-Robert Pocock 2015-03-03 16:29:55 UTC 
Created attachment 997581 [details]
File: core_backtrace
Comment 4 Bruce-Robert Pocock 2015-03-03 16:29:56 UTC 
Created attachment 997582 [details]
File: dso_list
Comment 5 Bruce-Robert Pocock 2015-03-03 16:29:57 UTC 
Created attachment 997583 [details]
File: environ
Comment 6 Bruce-Robert Pocock 2015-03-03 16:29:58 UTC 
Created attachment 997584 [details]
File: exploitable
Comment 7 Bruce-Robert Pocock 2015-03-03 16:29:58 UTC 
Created attachment 997585 [details]
File: limits
Comment 8 Bruce-Robert Pocock 2015-03-03 16:29:59 UTC 
Created attachment 997586 [details]
File: maps
Comment 9 Bruce-Robert Pocock 2015-03-03 16:30:00 UTC 
Created attachment 997587 [details]
File: open_fds
Comment 10 Bruce-Robert Pocock 2015-03-03 16:30:01 UTC 
Created attachment 997588 [details]
File: proc_pid_status
Comment 11 Bruce-Robert Pocock 2015-03-03 16:30:02 UTC 
Created attachment 997589 [details]
File: var_log_messages
Comment 12 Egmont Koblinger 2015-03-03 18:56:54 UTC 
Can you recall what you had been doing previously in those terminals, and what you were doing when it crashed?

E.g. what was the app that you forced to close? Did it constantly produce output or stand still? Was there some ongoing activity in the other tabs/windows?

Can you perhaps reproduce the bug somehow?

(All the gnome-terminal windows are handled by a single process, if it crashes then all of them are gone, that's not a coincidence.)
Comment 13 Egmont Koblinger 2015-03-03 19:23:18 UTC 
Upstreamed: https://bugzilla.gnome.org/show_bug.cgi?id=745555
Comment 14 Fedora End Of Life 2015-11-04 13:20:44 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.
Comment 15 Fedora End Of Life 2015-12-02 09:40:39 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.