Description of problem: Every once in a while since I upgraded to F18 I get black rectangles instead of new windows for newly opened applications, including any pull down menu, such as search suggestions in Google in Firefox. Keyboard entry works fine, but I can't see what I'm doing. During these times if I attempt to open a video in a terminal with totem, gst123, or gst-launch-*, I get a segfault--other programs don't die, I just can't see what I'm doing. I checked dmesg, /var/log/messages, and /var/log/Xorg.0.log and don't see anything, but honestly I am very far from being an expert. Restarting the X server works for a time, but I don't know what's going on. It's possible this happens after the screen blanks, but again not always by any means. Version-Release number of selected component: totem-3.6.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: totem --debug 'Space Age_ Nasa\'s Story - 18-3 KLRU-Q - Mon 25 Mar 2013 12_05_01 AM CDT.mkv' crash_function: intel_miptree_unmap executable: /usr/bin/totem kernel: 3.8.4-202.fc18.i686.PAE uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #0 intel_miptree_unmap at intel_mipmap_tree.c:1752 #1 intel_unmap_renderbuffer at intel_fbo.c:178 #2 unmap_attachment at ../../../src/mesa/swrast/s_renderbuffer.c:609 #3 _swrast_unmap_renderbuffers at ../../../src/mesa/swrast/s_renderbuffer.c:681 #4 intelSpanRenderFinish at intel_span.c:164 #5 _swrast_render_finish at ../../../src/mesa/swrast/s_context.c:908 #6 _swsetup_RenderFinish at ../../../src/mesa/swrast_setup/ss_context.c:218 #7 run_render at ../../../src/mesa/tnl/t_vb_render.c:326 #8 _tnl_run_pipeline at ../../../src/mesa/tnl/t_pipeline.c:163 #9 intelRunPipeline at intel_tris.c:1086
Created attachment 730161 [details] File: backtrace
Created attachment 730162 [details] File: cgroup
Created attachment 730163 [details] File: core_backtrace
Created attachment 730164 [details] File: dso_list
Created attachment 730165 [details] File: environ
Created attachment 730166 [details] File: limits
Created attachment 730167 [details] File: maps
Created attachment 730168 [details] File: open_fds
Created attachment 730169 [details] File: proc_pid_status
Created attachment 730170 [details] File: var_log_messages
Created attachment 730171 [details] File: xsession_errors
Created attachment 732959 [details] output from gst-launch-1.0 during another instance
I think it's a generic Mesa/OpenGL bug for Intel drivers; see https://bugzilla.redhat.com/show_bug.cgi?id=922224
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.