I have found some artifacts:
1. The first is always reproducable:
Black (and sometimes red) squares appear in the "Transform Properties" popup.
To recreate:
(Load file or Erase all and Add.Mesh.Cube)
press N to bring up Properties popup.
(press TAB to) enter Editing mode.
Move mouse back and forth over the Properties popup. Nothing happens.
Press Z to turn on shading.
Now move mouse over the Properties popup, sometimes rapidly.
The area below OB:Cube and above Median.X turns black, and the Local button disappears.
Move the mouse over the Local button location, and it reappears.
Moving the mouse around causes the black artifact to appear and disappear.
and can also appear between OB:Cube and Par:
and between Median.Z and Median.Crease
With a single vertex selected, the Vertex.XYZ areas also turn black.
In fact, no field in the popup is exempt from disappearing.
The key is shading in the same pane that has the popup.
Description
Event Timeline
Logged In: YES
user_id=5445
The second instance of artifacts goes like this:
The prerequisite may include visiting Scripts.System.ConfigEditor and/or getting python errors.
I wonder if python is used at all, in drawing the screen?
Either way, at this point, I suspect it is part of the trigger.
The symptoms went like this:
First occurrence:
Prelude:
After changing the top bar (User Preferences) to Scripts Window, and menu selecting Scripts.System.ConfigEditor (at least twice)
dragging the border handle down so the top pane is visible. Visiting different settings, console, etc.
Then dragging it back up.
I forget if I changed the top menu bar back and forth between functions.
Symptoms:
First the black lines become transparent.
Noticeable in the borders between panes, and some lettering in the top 2 menu bars.
Next, I clicked on the arrow to expand/contract the menu items,
and the menu bar background was not refreshed properly. There was overlapping text.
Moving the mouse around caused the black (now transparent) lines to flicker, I could see the previous contents of the top pane. as it was before I dragged the border handle back to the top.
I closed and restarted Blender that time.
Second occurrence:
Prelude:
After reproducing the 1st artifact, and generating python errors because of a missing material, and visiting the ScriptsConfigEditor a few times, using the top menu bar again as described above,
I Alt-Tabbed to an Eterm to view the console/output messages.
Upon Alt-Tabbing back to Blender:
Symptoms:
The black pane borders again turned transparent.
I could see the eterm window beneath blender.
New symptoms occurred after left-clicking on the 3dview menu bar, in a blank part to the right of the buttons, immediately, the entire screen went black, except for that menu bar.
With fingers off the mouse buttons, just moving the mouse around caused parts of the screen to go black and come back, especially when moving over black (now transparent) lines.
At some point, the screen stayed visible again when over non-black areas, like in 3d-view. and moving the mouse around the 3d view caused portions of the lower panel-buttons to go black between fields, exactly like in the properties popup earlier described.
I clicked again on the menu bar and duplicated the screen going all black.
After satisfying this sequence and symptoms, I closed blender to try again to duplicate it. but have been unable to find the exact trigger.
Logged In: YES
user_id=4290
It sounds like you have some OpenGL problems, probably driver issues. Try changing (i.e. updating) the drivers for your graphics card.
Also, which os/graphics-card is this on?
Logged In: YES
user_id=5445
linux-2.4.33.3
nvidia-8762
X-org-7.0
glibc-2.3.2
I'll look into newer versions.
Logged In: YES
user_id=103
Yes you definitely have an opengl error.
Check on blender.org -> support -> faq, the "nvidia noflip".
Logged In: YES
user_id=5445
While setting noflip does reduce the number of occurances of the bug, to about 1/2 or 1/4 of the time, it is definitely still there.
One difference, is instead of black squares or areas, the background is now visible in a rainbow distorted spectrum of the lines and vertices.
Are you sure this issue should be closed?
Logged In: YES
user_id=103
I am 100% sure we dont have a blender bug, but a support issue :)
Be asured blender runs fine, with identical opengl code for all platforms. Just matter of finding the right way to set your drivers.
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.
Looks like 2.5 requires a gcc and/or libc upgrade. I won't have an answer for a while...