Red Hat Bugzilla – Bug 978071
[abrt] Terminal-0.4.8-4.fc18: handle_error: Process /usr/bin/Terminal was killed by signal 5 (SIGTRAP)
Last modified: 2014-02-05 18:12:19 EST
Description of problem:
Application froze. I tried to close the program with the x button, then it crashed.
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Jun 25 18:52:36 cirno abrt: Saved core dump of pid 1768 (/usr/bin/Terminal) to /var/tmp/abrt/ccpp-2013-06-25-18:52:34-1768 (40198144 bytes)
Thread no. 1 (10 frames)
#4 handle_error at xcb_io.c:213
#5 handle_response at xcb_io.c:325
#7 XTranslateCoordinates at TrCoords.c:51
#8 gdk_window_x11_get_root_coords at gdkwindow-x11.c:2874
#9 gdk_window_get_origin at gdkwindow.c:8346
#10 vte_terminal_paint at vte.c:11174
#11 vte_terminal_expose at vte.c:11343
#12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#17 gtk_widget_event_internal at gtkwidget.c:5017
#18 gtk_widget_send_expose at gtkwidget.c:4846
Created attachment 765312 [details]
Created attachment 765313 [details]
Created attachment 765314 [details]
Created attachment 765315 [details]
Created attachment 765316 [details]
Created attachment 765317 [details]
Created attachment 765318 [details]
Created attachment 765319 [details]
Created attachment 765320 [details]
Can you think of anything you were doing before it froze?
Can you duplicate it?
(In reply to Kevin Fenzi from comment #10)
> Can you think of anything you were doing before it froze?
> Can you duplicate it?
I was running gparted which was scanning my only drive for partitions. I had at least two terminals open, one had a job running. I tried to launch another terminal using a keyboard short cut. The window was created, but my prompt did not show. I then tried to close the windows using the x button, but it did not respond.
I was able to reproduce it when gparted was preforming a partition move. I think that this might have been because of high drive I/O. That's about all I can think of. I hope this helps.
ok. Thanks for the report, will see what I can make of it...
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Thank you for reporting this bug and we are sorry it could not be fixed.