--nextPart3522659.ASHzxYLy5G
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

 since some weeks I started to see annoying lockups in trunk. This means=20
that the mouse cursor cannot be moved for a while, or you move the mouse=20
and the cursor follows it with a long delay. Switching to a terminal=20
with CTRL-ALT-Fx is also hard and takes a while until it happens. After=20
a while (a minute or so) things return to normal. I found how to=20
reproduce it, but I'm unsure what is broken: KWin, Konsole, Plasma or=20
the Nvidia binary drivers.
 To reproduce, you need to have a running Konsole.  One way to reproduce=20
is to start two sessions (tabs) inside one Konsole and switch between=20
the tabs. You might need to switch more than once. Sometimes you might=20
see black screen for a while.
 The other, easier but harder to get rid of it, solution is to start top=20
inside a konsole session. The problem appears for some other commands in=20
konsole, like running cmake, switching directories, some operations in=20
mc.

 The problem is that I cannot really identify which component is guilty.

1) The 169.12 and 173.14 drivers (the two latest stable drivers) show=20
the problem. The 173.08 (a beta driver) doesn't show it. So it indicates=20
a driver issue.

2) Konsole trunk shows the problem under trunk (with the guilty=20
drivers). For some reason I cannot start konsole 4.0.4 from under trunk,=20
it starts the trunk version...=20

3) Konsole KDE3 under trunk has no problems.

4) Konsole 4.0.4 under KDE 4.0.4 has no problems

5) removing plasmarc, konsolerc does not help

6) removing kwinrc helps

1) and 6) makes me think is a kwin + composite + nvidia issue. The=20
problem here is:
1) desktop effects disabled on login - no problem
2) dekstop effects enabled on login - problem is visible
3) dekstop effects enabled on login, but disabled afterwards - problem=20
remains
4) desktop effects disabled on login and turned on afterwards - no=20
problem

5) opengl or xrender setting: I can't decide whether they make a=20
difference. I saw the problem, switched to xrender, problem gone=20
away.Logged out/logged in - problem reappears. If in case 4) I turn on=20
the effects, it works both with opengl and xrender.

If I log in through ssh and monitor CPU usage with top, I see either=20
Xorg going up to 100% (still I have dual core CPU, why does it lock=20
completely?), or some random process using 99% (hal-addon-storage,=20
usbstorage).

What can I do aside of turning off desktop effects or use the beta driver?=
=20
There must be something that changed between KDE 4.0.4 and trunk that=20
causes the problems. Also I'm clueless why it happens only with konsole.


I hope somebody with knowledge about the composition stuff has an idea=20
what is going on.

System details:
Opensuse 11.0 (rc1)
Nvidia Geforce 7600 GS
Opteron 180 dual-core
Nvidia binary driver (see versions above)
=46rom xorg.conf:
  Option        "NvAgp" "1"
  Option        "AddARGBGLXVisuals" "True"
  Option        "UseCompositeWrapper" "true" //this doesn't change=20
anything
[...]
   Option       "Clone" "off"
  Option       "Xinerama" "off"
[...]
 Option       "Composite" "on"

Andras
=2D-=20
=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org


--nextPart3522659.ASHzxYLy5G
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iD8DBQBIQVHnTQdfac6L/08RAkhhAJ9eKI8FdsCYwJG0F+O86ipDIKH2CQCeNP+8
GB1IiMY4yTjAHaTfktukth0=
=a2+R
-----END PGP SIGNATURE-----

--nextPart3522659.ASHzxYLy5G--