Summary: | [Intel 945GME/x86] xf86-video-intel update from 2.7.99.901 -> 2.7.99.902 and xserver update from 1.6.1.901 > 1.6.2 breaks blender | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jonas Thiem <contact> |
Component: | Drivers/DRI/i915 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jonas Thiem
2009-07-27 23:41:38 UTC
glxinfo says the Mesa version is 7.5, but as that doesn't seem available in the version box I left it unspecified there (In reply to comment #0) > On Archlinux, updating the intel driver from version 2.7.99.901 -> 2.7.99.902 > and the xserver from 1.6.1.901 to 1.6.2 (those updates have been packaged that > way that they depend on each other) breaks the blender UI (2d parts). > > This means that when hovering or clicking at any button of the blender GUI, > blender won't refresh the screen anymore which means it is impossible to open > any menus at all (the GUI is pretty much unusuable). I could reproduce this on my test machine which is a Q35, my configuration is: Libdrm: (master)9aed44beeac4f250a58c792d64a4dee1dde3d086 Mesa: (master)1ee3bcfff08599961c69549a1ad699c02df49bec Xserver: (master)b3751454cbe02ee952bab213e8c3684d429c41b3 Xf86_video_intel: (master)8084f76d86f048ca5b82da089fffa9665dbbcdd5 > > The 3d view works flawlessly and doesn't seem to be affected. Reverting the > intel driver and xserver version fixes things, reverting blender from 2.49a to > 2.48a not, so it doesn't seem to be directly caused by an update of blender > itself. > > (I hope this bug is in the right category, as blender is an OpenGL app I > thought this might be the right place for my first bug report. Otherwise please > recategorize accordingly) > For reference, software rendering works fine: LIBGL_ALWAYS_SOFTWARE=1 blender |
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.