[Bug 364479] [NEW] Corrupted X after enabling UXA, unable to log into KDE

[Oenologist]

Public bug reported:

Binary package hint: xserver-xorg-video-intel

The problem is the following: a few days ago, irritated by the sluggish
performance of Jaunty I decided to switch on the UXA option in Xorg. It
worked flawlessly, but when I started to change the brightness options
in KDE, suddenly sounds became distorted and KWin notified an error.
Since then it is not possible to log into KDE - 2-3 icons appear on
startup splash and everything goes back to login screen, accompanied by
various graphic glitches (I'm also unable to go into terminals with
CTRL+ALT+F#, these are blank screens or have green stripes/glitches).
Finally, I managed to make KDE operational again by removing the Intel
driver. Everything seems to work fine except for the desktop effects.
Now, everytime I install the driver (be it 2.4 or the one in repos) the
problem returns and it is impossible to log to KDE again.

Is it then a persistant corruption of the driver itself? Perhaps some
unwanted modifications in xsessions? My xorg is totally basic, with no
extra lines (I will attach it below). While using UXA I experienced no
errors/problems everything worked splendidly while performing basic
multiwindow tasks with desktop effects enabled.

So, is it possible to revert into 'old' settings which made the
operation of Intel driver possible?

Dell Inspiron 1525

$ lsb_release -rd
Description:	Ubuntu 9.04
Release:	9.04

$ uname -a
Linux dell-desktop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

** Affects: xserver-xorg-video-intel (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Corrupted X after enabling UXA, unable to log into KDE
https://bugs.launchpad.net/bugs/364479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs