If you have Assistive Technologies (accessibility/a11y) enabled, certain conditions will cause gnome-terminal to suddenly exit(1). For example, hitting 'Tab' after running 'alsamixer -c0' will cause gnome-terminal to suddenly exit.
A much simpler reproducer: type (or cut-and-paste) ♥ into a gnome-terminal window, then hit backspace.
A little debugging shows that gnome-terminal is being forcibly disconnected from dbus - at the time of the crash, gnome-terminal still has its end of the socket open, but dbus is closing its end of the socket as a result of getting DBUS_WATCH_ERROR|DBUS_WATCH_HANGUP from dbus_watch_handle.
Further messing around with dbus-monitor --session shows that, under normal circumstances (like backspacing over the letter 'f'), pressing backspace results in (among other things) the following two signals:
signal sender=:1.144 -> dest=(null destination) serial=369 path=/org/a11y/atspi/accessible/90; interface=org.a11y.atspi.Event.Object; member=TextCaretMoved
[some data here]
signal sender=:1.144 -> dest=(null destination) serial=370 path=/org/a11y/atspi/accessible/90; interface=org.a11y.atspi.Event.Object; member=TextChanged
variant string "f"
object path "/org/a11y/atspi/accessible/root"
When backspacing over the '♥', the TextCaretMoved signal is sent, but the subsequent TextChange/"delete" signal never happens; instead the following signal is:
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=42 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
which indicates gnome-terminal being thrown off the bus, probably for attempting to send malformed utf8. I'm guessing (or, rather, halfline guessed, and it makes sense because he's far more clever than I am) that only the last byte of the '♥' sequence is being sent, which is invalid utf8, which would cause dbus to reject the message.
So.. I guess this might actually be a vte/a11y bug, but I don't know how the gnome-terminal/a11y code is structured, so I'm leaving it here.
Filed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=627591
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: