Version-Release number of selected component:
libreport version: 2.0.18
:Thread no. 1 (10 frames)
: #0 g_logv at gmessages.h:101
: #4 handle_error at xcb_io.c:212
: #5 handle_response at xcb_io.c:324
: #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:8340
: #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
Created attachment 662673 [details]
Created attachment 662674 [details]
Created attachment 662675 [details]
Created attachment 662676 [details]
Created attachment 662677 [details]
Created attachment 662678 [details]
Created attachment 662679 [details]
Created attachment 662680 [details]
Created attachment 662681 [details]
Created attachment 662682 [details]
Created attachment 662683 [details]
Created attachment 662684 [details]
What were you doing when this happened?
Can you duplicate it?
I just reproduced it now.
It is pretty easy to reproduce. Open 'Terminal' from the menu. Do nothing. Wait an hour or so and abrt will notify me that it has crashed.
I mean I did nothing inside of the terminal, merely opened it and let it sit there for a while. I'm not sure if there is something else running on the computer that interacts with it somehow.
I'll try running it from the command line to see if it gives me some sort of error message when (if) it crashes again.
(Terminal:21761): Gdk-ERROR **: The program 'Terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 3871 error_code 9 request_code 148 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
What video driver are you using?
Can you attach your /var/log/Xorg.0.log ?
Created attachment 663186 [details]
ok, no help there, that looks completely normal.
can you now attach 'glxinfo' and a 'ps aux' outputs?
Created attachment 663791 [details]
Created attachment 663792 [details]
All looks pretty normal there. ;(
Does this happen to any other terminals? gnome-terminal, roxterm, etc?
Well, I've restarted X Windows and now I can't reproduce it any more.
But it was only in Terminal, not in konsole or any of the other terminal programs.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.