Xgl very slow, even when running only metacity (Intel i810)

I have the same problem following an update on 8/31/07. The only difference is I'm using the xserver-xorg-video-intel driver.

I tried it with both drivers and had the exact same outcome.

Hi Christoph,
thanks for the hint, I also spent quite a lot of time to search for the sluggishness of my X.

I have:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)

And:
ii xserver-xorg-video-i 2:2.1.1-0ubuntu2 X.Org X server -- Intel i8xx, i9xx display driver
(Thats the one I am using ...)

Off-Topic; Are you able to suspend and resume? On resume I have to use powersaved's featiure to switch VT - then my X backlight comes back, but the console are not init-ed anymore.

rgds,
Andreas

Hi,
I had the same problem on a Dell Inspiron 510m, with an Intel 855GM:

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

I tried both i810 and intel drivers on Xgl without success, I solved uninstalling Xgl and using the Xorg server.

Same experience here with both intel and i810 drivers. Card is a 82865G. Also solved with apt-get remove xserver-xgl.

The computer was almost unusable due to this bug, scrolling a window in the browser would take lots of time and 100% CPU, so I'd say this may be a big issue for non-technical people hitting it.

I forgot to add: this happened using kubuntu, caused by upgrade to gutsy.

Is there any particular reason to use xgl-server with free intel drivers ?
The only people who need Xgl to run compiz are those using the fglrx drivers.

The most strange thing is that on my Intel 915GM the direct rendering is disabled if i am using xserver-xgl,
but with out it's back to normal again:

quetzal@orion:~> cat xgl.bug | grep direct
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa GLX Indirect

quetzal@orion:~> glxinfo | grep direct
direct rendering: Yes

Once again, could you please explain why you are using xserver-xgl ?

This is a default on Gutsy.

In my case it was pulled in by the update to gutsy. I don't really know what for or what I'm losing by removing it.

I'm closing this bug.
Just uninstall xserver-xgl to make it go away, you don't need it with the intel drivers.
It is _not_ installed by default in Gutsy.

Then I understand that either

a) something else pulled Xgl in when upgrading.
b) it was previously installed and only exhibited the problem after the upgrade.

On second thinking, a) cannot be since removing Xgl didn't pull out anything else due to dependencies.

In truth, I don't remember explicitly installing Xgl but I couldn't rule it out either. Is there some way to inspect the lifetime of a package in the system? First install, reason, things like that (note that I have already removed it)? My machine started with Dapper.

As a side note, if b) is what happened, should someone be notified about it? Is it normal that Xgl has no effect in feisty and cripples X in gutsy for this card?

I'm sure for me the switch from X to Xgl was due to some updates in
Gutsy development. Either the bug or the switch to Xgl happended around
2007.09.04 - probably the switch.
If Xgl is not the default in Gutsy, at least for the i810 driver, you
can close this as "won't fix" or something like that.
I haven't tried with the new intel driver.

.Andrea

mosteo wrote:
> Then I understand that either
>
> a) something else pulled Xgl in when upgrading.
> b) it was previously installed and only exhibited the problem after the upgrade.
>
> On second thinking, a) cannot be since removing Xgl didn't pull out
> anything else due to dependencies.
>
> In truth, I don't remember explicitly installing Xgl but I couldn't rule
> it out either. Is there some way to inspect the lifetime of a package in
> the system? First install, reason, things like that (note that I have
> already removed it)? My machine started with Dapper.
>
> As a side note, if b) is what happened, should someone be notified about
> it? Is it normal that Xgl has no effect in feisty and cripples X in
> gutsy for this card?
>
>