[pkg-nvidia-devel] Bug#443674: System freezes with nvidia-glx-100.14.19 unexpectedly

[Hans]

Package: nvidia-glx
Version: 100.14.19-1
Severity: grave



-- Package-specific info:
uname -r:
Linux protheus2 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 GNU/Linux


/proc/version:
Linux version 2.6.22-2-amd64 (Debian 2.6.22-4) (waldi at debian.org) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Thu Aug 30 23:43:59 UTC 2007


/proc/driver/nvidia/version:


03:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce Go 7300 (rev a1)


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.iso885915 at euro, LC_CTYPE=de_DE.iso885915 at euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages nvidia-glx depends on:
ii  libc6               2.6.1-5              GNU C Library: Shared libraries
ii  libx11-6            2:1.0.3-7            X11 client-side library
ii  libxext6            1:1.0.3-2            X11 miscellaneous extension librar
ii  nvidia-kernel-2.6.2 100.14.19-1+2.6.22-4 NVIDIA binary kernel module for Li
ii  x11-common          1:7.3+2              X Window System (X.Org) infrastruc
ii  xserver-xorg-core   2:1.4-2              X.Org X server -- core server

nvidia-glx recommends no packages.

-- no debconf information
Dear maintainers,

I sadly have to tell you, that the newest package "nvidia-glx" version
100.14.19 is causing to freeze the whole system unexpectedly.
I found out, this is, when many changes in the content of a browser or a
picture appear (somebody wrote about this, too).

The package is definately NOT in the nvidia-kernel-source, nor in the
kernel itself, it can be proved to be in nvidia-glx.

There is also no log available, where you can see, what is happening.

This bug can be found in versions 100.14.11 and 100.14.19, see also
bug number 432182. It has been reported, this behaviour is on other
distributions, too (I heard of Arch-Linux).

The workaround is, to switch back to 100.14.09, which is running stable and
without no errors.

Please contact me, if I can help you.

Best regards

Hans-J. Ullrich