intel graphics, external monitor, vmware don't start, wine is slow at startup

[Hans Englhauser]

Ubuntu 11.04 is running on a Lenovo Thinkpad T500 with internal intel graphic card. My laptop is connected to an external monitor. Most applications run well, except

- wine is slow on startup when calling a windows application, but after 15 seconds, my windows appications are executed in normal speed. I checked this with version 1.2 and 1.3.15

- when starting a virtual machine with vmware player 3.1.4, it only display a black window but the virtual machine don't start.

After unpluging the external monitor, wine starts with normal speed and the virtual machine start at all. It was not neccessary to reboot my T500 to get the applications run. In Ubuntu 10.10, I had no problem with wine nor vmware. Because two well known applications have their problem with ubuntu 11.04, the bug is in ubuntu intel graphic driver.

Hans

[Pushkin (kovshovik-alexandr)]

Same problem here. I've got Intel HD graphics 3000 (integrated in my Core i7 2600K CPU) and I've got exactly the same problem: when any wine application starts up, my mouse movement freezes even. I have a desktop computer with 2 external monitors: one is 1280x1024 and another one is 1920x 1200.

I'm running Ubuntu 11.04 x64 bit, wine 1.3.15.

Windows application that I tried: Heidi SQL, MS Word 2007, MS Excel 2007.

Please let me know how can I help resolve this issue - I'll provide logs, dumps, etc. if necessary.

[Hans Englhauser (0-hans-f)]

Totem video player is the same. With dual head, it freeze for 5 to 10 seconds while starting. VLC don't freeze. TeamViewer use wine, so it freeze, too.

[Hans Englhauser (0-hans-f)]

A solution for wine was sent to me by support of TeamViewer:

in wine, add this to Windows registry:

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"UseXVidMode"="N"
"UseXRandR"="N"

The key has to be created. Since I added this to Registry, all Windows applications start in normal speed. But there are still issues in Totem and VMware. But I think this workaround for wine points directly to the bug.

Hans

[Chris Wilson (ickle)]

The bug is that wine simply spammed xrandr probes, which are expensive as they have to query hardware state.