with: xorg-edgers Checkout from git 20091110 (master branch) up to commit 520b6abdecdaba856e5ca04938e18eb83b33dfaa blender-2.49b-linux-glibc236-py26-x86_64 ubuntu 9.10 karmic All the menus like "File", "Help", "View", "Object" and the window type selection menu (leftmost icon) are not displayed at all. They are there and can be used blindly.
This is marked as a regression. Do you have a commit SHA1 when it worked? Could you bisect to find the bad commit?
digging for old packages in xorg-edgers ppa showed: libgl1-mesa-dri: Installed: 7.7.0~git20091103.c475079e-0ubuntu0tormod is bad libgl1-mesa-dri: Installed: 7.7.0~git20091031.1cc16e1b-0ubuntu0tormod is good That is as far as I can go, I think. Sadly no bisect powers here.
I'm having the same problem, bisecting finds this: bcbfda71b03303d3f008a6f3cf8cb7d9667bf8d2 is the first bad commit commit bcbfda71b03303d3f008a6f3cf8cb7d9667bf8d2 Author: Brian Paul <brianp@vmware.com> Date: Mon Nov 2 12:40:04 2009 -0700 intel: avoid unnecessary front buffer flushing/updating Before, if we just called glXMakeCurrent() and didn't render anything we'd still trigger a flushFrontBuffer() call. Now only set the intel->front_buffer_dirty field at state validation time just before we draw something. NOTE: additional calls to intel_check_front_buffer_rendering() might be needed if I missed some rendering paths. :040000 040000 4a5b942c62743d0175d6a75d1ad4dc15d1a42f92 d5b7b15e61c600b9531431bc7345ecd69fe46cb2 M src
I also have the same problem on i915 and i965 platform.
increase priority and hope this could be fixed before 7.7 rc1.
commit a7e4a311e971005f7b23572ff3ca93f6d3c17edf Author: Eric Anholt <eric@anholt.net> Date: Wed Dec 2 11:56:18 2009 -0800 intel: Fix more front-buffer rendering after Brian's less flushing patch. bcbfda71b03303d3f008a6f3cf8cb7d9667bf8d2 left out many blit paths. This fixes up more of them to get Blender to work again. Bug #25030.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.