mate-terminal: g_type_check_instance_is_a(): mate-terminal killed by SIGSEGV

[raveit65]

fedora report:
https://bugzilla.redhat.com/show_bug.cgi?id=1085985

 liuyuqi.crh@gmail.com 2014-04-09 15:44:27 EDT

Description of problem:
I kept mate-terminal open without use for a few days, then I typed in "cd" (in bash shell) and it exited.

Version-Release number of selected component:
mate-terminal-1.6.2-1.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        mate-terminal
crash_function: g_type_check_instance_is_a
executable:     /usr/bin/mate-terminal
kernel:         3.12.5-302.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_is_a at gtype.c:3975
 #1 gtk_widget_get_parent at gtkwidget.c:6483
 #2 sync_tab_label at terminal-tab-label.c:73
 #3 g_cclosure_marshal_VOID__PARAM at gmarshal.c:1042
 #9 g_object_notify_queue_thaw at gobject.c:292
 #10 g_object_thaw_notify at gobject.c:1278
 #11 vte_terminal_emit_pending_signals at vte.c:14758
 #12 vte_terminal_process_incoming at vte.c:4402
 #13 time_process_incoming at vte.c:14766
 #14 process_timeout at vte.c:14813

 Wolfgang Ulbrich 2014-06-21 11:35:25 EDT

Looks like a needed process for bash has been ended after some days.
Is there a valid reason why you let mate-terminal open witout using it?

 liuyuqi.crh@gmail.com 2014-06-21 14:56:31 EDT

(In reply to Wolfgang Ulbrich from comment #12)
> Looks like a needed process for bash has been ended after some days.
> Is there a valid reason why you let mate-terminal open witout using it?

I was working on my homework for several days in a row, so I just kept my terminals open so that I can resume my work once I get back to my computer. However I do have one terminal open for a specific task, and I switch from terminals so that I can do more than one homework concurrently. Sometimes I just leave some terminals on for a few days... I saw the pop-up window by abrt and I reported it as expected.

btw is the information provided not specific enough to figure out where the problem is?

Thanks!

Pls ask at original report for questions to user.
I will say the same in fedora report.

[monsta]

1.6.2... it's EOL now.