Your message dated Sun, 28 Nov 2010 20:43:39 +0100
with message-id <[email protected]>
and subject line Re: nvidia: 800x600 uses too high a refresh rate for LCD 
monitors
has caused the Debian Bug report #541681,
regarding nvidia: 800x600 uses too high a refresh rate for LCD monitors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
541681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541681
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: extremetuxracer
Version: 0.4-2
Severity: grave
Justification: renders package unusable


If I try to star etracer I get a black screen. The desktop is frozen. 
I  must restart the X-server again to do anything. 
Maybe the problem is in the 3D-acceleration.
My graphic card is a nvidia GeForce 6200.
I use the following nvidia package
nvidia-glx                                      install
nvidia-kernel-2.6.26-1-amd64                    install
nvidia-kernel-common                            install
nvidia-kernel-source                            install
nvidia-xconfig                                  install

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

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages extremetuxracer depends on:
ii  extremetuxracer-data   0.4-2             data files for the game Extreme Tu
ii  libc6                  2.9-23            GNU C Library: Shared libraries
ii  libfreetype6           2.3.9-5           FreeType 2 font engine, shared lib
ii  libgcc1                1:4.4.1-1         GCC support library
ii  libgl1-mesa-glx [libgl 7.0.3-7           A free implementation of the OpenG
ii  libglu1-mesa [libglu1] 7.5-3             The OpenGL utility library (GLU)
ii  libice6                2:1.0.5-1         X11 Inter-Client Exchange library
ii  libpng12-0             1.2.38-1          PNG library - runtime
ii  libsdl-mixer1.2        1.2.8-6           mixer library for Simple DirectMed
ii  libsdl1.2debian        1.2.13-4+b1       Simple DirectMedia Layer
ii  libsm6                 2:1.1.0-2         X11 Session Management library
ii  libstdc++6             4.4.1-1           The GNU Standard C++ Library v3
ii  libx11-6               2:1.1.5-2         X11 client-side library
ii  libxext6               2:1.0.4-1         X11 miscellaneous extension librar
ii  libxi6                 2:1.2.1-2         X11 Input extension library
ii  libxmu6                2:1.0.4-1         X11 miscellaneous utility library
ii  libxt6                 1:1.0.5-3         X11 toolkit intrinsics library
ii  tcl8.5                 8.5.7-1           Tcl (the Tool Command Language) v8
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

extremetuxracer recommends no packages.

extremetuxracer suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Wednesday, 25. August 2010 06:09:35 Andreas Beckmann wrote:
> On Sunday, 23. August 2009 16:15:20 Steve Cotton wrote:
> > Transferring to the nvidia-glx package, I think they're the best
> > people to decide what to do with the bug.  The documentation for
>
> ...
>
> > Stefano is seeing this with (I assume) the Debianized package.
> > I'm happy to add debug too, but my own system is running a
> > straight-from-Nvidia driver (version 180.51).
>
> Is this problem still present with the current versions of X.Org and the
> NVIDIA driver? 195.36.31-2 entered unstable yesterday.

Since we haven't heard from the submitter since we asked for more information 
a few months ago, I assume the problem does no longer exist and I'm closing 
this report now.
If the problem is still reproducible with current driver versions (195.36.31-6 
in testing/unstable or 260.19.21-1 in experimental), feel free to reopen this 
bug report.


Andreas


--- End Message ---

Reply via email to