Your message dated Sat, 5 Jun 2010 15:41:51 +0200
with message-id <[email protected]>
and subject line Re: Bug#141135: nvclock: NVClock corrupt text mode font when
run
has caused the Debian Bug report #141135,
regarding nvclock: NVClock corrupt text mode font when run
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.)
--
141135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=141135
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvclock
Version: 0.5-1
Severity: normal
When running nvclock on my graphics board, the text mode font is corrupted.
It appears that it's only lowercase characters and symbols. This occurs
regardless of clock speed (I use the program to underclock my board for
stability). Previous versions (0.4.2) did not have this problem.
lspci reports my card as a:
01:00.0 VGA compatible controller: nVidia Corporation GeForce 256 (rev 10)
-- System Information
Debian Release: 3.0
Kernel Version: Linux stimpy 2.4.18 #1 Sun Mar 10 12:23:27 GMT 2002 i686 unknown
Versions of the packages nvclock depends on:
ii libc6 2.2.5-3 GNU C Library: Shared libraries and Timezone
ii libglib1.2 1.2.10-4 The GLib library of C routines
ii libgtk1.2 1.2.10-10 The GIMP Toolkit set of widgets for X
ii xlibs 4.1.0-14 X Window System client libraries
--- End Message ---
--- Begin Message ---
On Wednesday, 30. October 2002 12:27:02 Paul M Sargent wrote:
> Hi there,
>
> Sorry about the delay in getting back to you on this.
>
> I'll give things a go, bu tI worked around the bug a long time ago by
> switching to VESA modes for my console.
>
> Regardless, I'll try to reproduce the error.
Since we didn't hear anything new on this problem for more than seven years I
assume this bug was fixed long ago and I'm closing this report now.
Andreas
--- End Message ---
