Your message dated Sun, 20 Mar 2011 17:56:56 +0100 with message-id <20110320165656.GY7161@const.famille.thibault.fr> and subject line Re: Bug#273192: swapped colors with 2.6 kernel has caused the Debian Bug report #273192, regarding swapped colors with 2.6 kernel 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 owner@bugs.debian.org immediately.) -- 273192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273192 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: swapped colors with 2.6 kernel
- From: Joey Hess <joeyh@debian.org>
- Date: Fri, 24 Sep 2004 00:06:39 +0200
- Message-id: <20040923220639.GA21698@kitenet.net>
Package: bogl-bterm Version: 0.1.18-1.1 Severity: normal Tags: d-i Several people here are seeing bterm come up in d-i with the blue and red colors swapped, so we get a red background normally and blue error screens. I think the other reporters were running oldworld powerpc, vmware, and I'm seeing it on my test laptop (i386). All of us using d-i with the 2.6.8 kernel. If we switch to another VC and switch back, the colors are corrected. -- see shy joAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 273192-done@bugs.debian.org
- Subject: Re: Bug#273192: swapped colors with 2.6 kernel
- From: Samuel Thibault <sthibault@debian.org>
- Date: Sun, 20 Mar 2011 17:56:56 +0100
- Message-id: <20110320165656.GY7161@const.famille.thibault.fr>
- In-reply-to: <20040923220639.GA21698@kitenet.net>
- References: <20040923220639.GA21698@kitenet.net>
We haven't had more reports recently (and some people have reported it as fixed). I believe this bug has somehow been fixed in the kernel itself. Samuel
--- End Message ---