Kwin compositing problem on maverick

I forget to say that when compositing is off the problems disappear.

interestingly I'm seeing this with a i945 since the updated libdrm - but even without using composition.

Upgrading to 4.5.2 via kubuntu-ppa these problems happen less frequently, but are still not solved. (maverick 64bit. intel i915)

I have similar issue with Intel GM965 integrated graphics.
Compositing is disabled after login. It is possible to activate compositing in System Settings / Desktop Effects.
After logout I've got black screen.

From my Xorg.0.log:

[ 20.383] (II) VESA: driver for VESA chipsets: vesa
[ 20.383] (II) FBDEV: driver for framebuffer: fbdev
[ 20.383] (++) using VT number 8

[ 40.249]
Fatal server error:
[ 40.249] xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call
[ 40.249]
[ 40.249]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[ 40.249] Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Exactly the same behavior as in Ihor Hayvuk's post but using Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03):
- compositing off on startup (can be enabled and starts normally if checks disabled in the configuration)
- artifacts and refreshing problems in yakuake, chrome and various other apps
- blank screen on logout

What about opengl performance?
I opened bug #663197, am I the only one with this problems?

I've heard about a user who has made improvements in performance and solve some problems related to artifacts, screen refreshes and corruptions installing the driver xserver-xorg-video-intel (2:2.13.901+git20101105~glasen~maverick~ppa1) from these PPA repositories:

https://launchpad.net/~glasen/+archive/intel-driver

The link where the user says it is:
http://www.kubuntu-es.org/foro/201011/problemas-video-integrado

With Glasen's driver and kde 4.5.3 from kubuntu-ppa the refresh seems correct (i'm testing since 2 hours) - Maverick 64 Intel i915

I also confirm this - the latest xserver-xorg-video-intel and libdrm2 packages from the Glasen PPA make Kwin's behaviour much more civilized.

I would like to confirm this as well. Over the last couple of days, I've seen artifacts only once or twice and they are likely to be caused by something else.

For those of you using Kubuntu, can any of you add «export QT_GRAPHICSSYSTEM="raster"» to ~/.xsessionrc, restart the computer and tell me if the problem still seems corrected with Glasen's PPA?

WARNING: worst case scenario you may not be able to edit the file again using the graphical interface; either disable the Desktop Effects with CTRL+ALT+F12 or edit it in a 'true' terminal and then reboot.

Hi,

* I just want to confirm that using Glasen's PPA solved all the screen refresh issues on my Kubuntu system (maverick on tablet PC EliteBook 2740p).

* Pedro: the QT_GRAPHICSSYSTEM line in the .xsessionrc did not seem to change anything.

* Everything is not perfect yet: I have "hung GPU" problems from time to time (probably related to bug https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/644740). More precisely, up to now I got a hung GPU when using "preview thumbnails" in the application panel or the "present window" effect. Disabling these two effects made my system almost stable.

Updating the intel X driver with the lasted version from ppa:ubuntu-x-swat/x-updates repository seem to solve the issue.

And also, the bug #662071 seem to be a duplicated of this bug.

Ok it seems to resolve the problems with xserver-xorg-video-intel 2:2.13.901-2ubuntu2~xup~maverick.

But note that with bleeding edge intel-driver from ppa:glasen/intel-driver (2:2.14~glasen~maverick~ppa6),
there is still graphics problem with emacs : the cursor takes the shape of the letters (with 'space' character the cursor disappear) !? (and have other refresh problems)
And when I disable compositing effects, this problem disappear.

I hope this bug will not reappear on a future stable release.

Hey Eric,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

This is still a problem in natty.

This bug was fixed but not for natty...