Bug#107208: marked as done (xserver-xfree86: [rendition] striped corruption and broken VT switching on Verite 2100/2200 rev 6)
Your message dated Sun, 27 May 2007 10:01:10 +0200
with message-id <46593AC6.1020602@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Rendition Verite 2200 broken under X 4.1.0
- From: "B. Gajdos" <brian@chem.sk>
- Date: Tue, 31 Jul 2001 12:55:43 +0200
- Message-id: <200107311055.f6VAthgt000633@chem2.chem.sk>
Package: xserver-xfree86
Version: 4.1.0-1
Severity: important
Tags: sid
After upgrade from X 4.0.3 to X 4.1.0, screen became completely messed
(it appeared to be working what it should but I was unable to see anything
reasonable, just color stripes). I was even unable to return back to
console with ctrl-alt-backspace, the screen left messed but the machine
operated correctly. This bug was reproduced every time I started X 4.1.0
on the same machine.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux chem2 2.4.6 #1 Tue Jul 24 20:29:49 CEST 2001 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages xserver-xfree86 depends on:
ii debconf 0.9.91 Debian configuration management sy
ii libc6 2.2.3-9 GNU C Library: Shared libraries an
ii xserver-common 4.1.0-1 files and utilities common to all
ii zlib1g 1:1.1.3-15 compression library - runtime
--- End Message ---
--- Begin Message ---
Closing this bug since I didn't get any reply from the submitter (or
repliers) after my ping about a month ago (except from people that don't
have the hardware anymore and thus can't try to reproduce).
Additionally, some addresses are now invalid.
If anybody ever reproduces this problem, feel free to reopen.
Brice
--- End Message ---
Reply to: