martin: Very nice! I installed driconf and changed the option "Synchronization with vertical refresh (swap intervals) to "Initial swap interval 0, obey application's choice". Resulting in the following ~/.drirc:
With these settings, the problem is gone. Can you confirm it also?
Wrt the upstream bug report and intel 2.6.0. The changes between 2.6.0 and 2.6.1 are very small, but I've tried git as well. I'll update that report.
Also, perhaps there's a chance that we'll end up with with dri2+uxa as default for jaunty (depending on what updates go to intel 2.6.2, 2.6.3, and when). That would solve this issue as well.
martin: Very nice! I installed driconf and changed the option "Synchronization with vertical refresh (swap intervals) to "Initial swap interval 0, obey application's choice". Resulting in the following ~/.drirc:
<driconf>
<application name="Default"> s3tc_enable" value="false" /> _mode" value="2" /> large_textures" value="2" />
</application>
<device screen="0" driver="i965">
<option name="force_
<option name="no_rast" value="false" />
<option name="fthrottle
<option name="bo_reuse" value="1" />
<option name="vblank_mode" value="1" />
<option name="allow_
</device>
</driconf>
With these settings, the problem is gone. Can you confirm it also?
Wrt the upstream bug report and intel 2.6.0. The changes between 2.6.0 and 2.6.1 are very small, but I've tried git as well. I'll update that report.
Also, perhaps there's a chance that we'll end up with with dri2+uxa as default for jaunty (depending on what updates go to intel 2.6.2, 2.6.3, and when). That would solve this issue as well.