Red Hat Bugzilla – Bug 975617
[abrt] mate-terminal-1.6.1-5.fc18: update_cursor: Process /usr/bin/mate-terminal was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-09 03:07:02 EDT
Description of problem:
All MATE terminals died immediately after resuming from suspend. No further clues as to triggering circumstances, sorry.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 update_cursor at gdkwindow.c:9543
#1 gdk_window_set_cursor at gdkwindow.c:8215
#2 vte_terminal_key_press at vte.c:5241
#3 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#8 gtk_widget_event_internal at gtkwidget.c:5017
#9 gtk_widget_event at gtkwidget.c:4814
#10 gtk_window_propagate_key_event at gtkwindow.c:5199
#11 gtk_window_key_press_event at gtkwindow.c:5229
#12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#17 gtk_widget_event_internal at gtkwidget.c:5017
Created attachment 762669 [details]
Created attachment 762670 [details]
Created attachment 762671 [details]
Created attachment 762672 [details]
Created attachment 762673 [details]
Created attachment 762674 [details]
Created attachment 762675 [details]
Created attachment 762676 [details]
Created attachment 762677 [details]
Created attachment 762678 [details]
Created attachment 762679 [details]
There's an issue with mate-power-manager we are debugging. Not sure if it's related.
Did this issue already ocours with mate-terminal-1.6.1-8.fc18 from updates-testing?
It hasn't reoccurred for me since the initial time, which was with the earlier package cited.
Ok, there was some changes with mate-power-manager, maybe it was related.
And on my systems it never happend.
Hope you agree with me to close the bug, if the issue ocours again i will re-open the report.
Thank you for reporting.