Your message dated Fri, 14 Jan 2005 07:09:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#290373: Debian Installation Report Template 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) -------------------------------------- Received: (at submit) by bugs.debian.org; 13 Jan 2005 20:33:12 +0000 >From [EMAIL PROTECTED] Thu Jan 13 12:33:12 2005 Return-path: <[EMAIL PROTECTED]> Received: from rproxy.gmail.com [64.233.170.206] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CpBea-0006mF-00; Thu, 13 Jan 2005 12:33:12 -0800 Received: by rproxy.gmail.com with SMTP id c16so267057rne for <[EMAIL PROTECTED]>; Thu, 13 Jan 2005 12:33:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=aR53IIRxktmHSqD7J09uIImhlnInbRLbqORAX1igmQlsFUwQs+ysHIlYiLHfOhFMmJaKJrpnqxBUYxcdo4ecmHmTRtmFAzwuzSK0cy2h4HCInICDtYruVTas1MyoLYPXvXSL9QJynPm2XfbCzncDIai7yKHrir0YYqJ0/fZsaOs= Received: by 10.38.151.26 with SMTP id y26mr197187rnd; Thu, 13 Jan 2005 12:33:11 -0800 (PST) Received: by 10.38.81.72 with HTTP; Thu, 13 Jan 2005 12:33:11 -0800 (PST) Message-ID: <[EMAIL PROTECTED]> Date: Thu, 13 Jan 2005 20:33:11 +0000 From: Pol Danilov <[EMAIL PROTECTED]> Reply-To: Pol Danilov <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Debian Installation Report Template Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: installation-reports Debian-installer-version: [2005-01-11] http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc2/sarge-i386-netinst.iso Date: [2005-01-11] Method: boot Netinstall CD-R, download packages off debian mirrors Machine: Compaq Presario 5140 Processor: Memory: 384 MB Root Device: 80 GB Maxtor IDE Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems: [O] Mount partitions: [O] Install base system: [O] Install boot loader: [O] Reboot: [O] Comments/Problems: One problem I had was getting my cordless USB mouse to work... I have a "Fellowes Cordless Notebook Mini Optical Mouse". It might have simply been faulty hardware because the problem resolved once I switched the connection to a different USB port. But when plugged into the "bad port"... It would say it detected a USB device on the port but that it couldn't enable it and told me "check the cord" or something. Kind of funny because there is no cord between the USB access point and the mouse. This error message was really annoying because it would print about every 30 seconds no matter what I had on the screen! It printed itself all over the blue configuration screens, etc so I couldn't see what I was doing. http://www.fellowes.com/FellowesAssets/Images/Catalog/Resize300/99197.jpg --------------------------------------- Received: (at 290373-done) by bugs.debian.org; 14 Jan 2005 06:55:45 +0000 >From [EMAIL PROTECTED] Thu Jan 13 22:55:45 2005 Return-path: <[EMAIL PROTECTED]> Received: from onera.onera.fr [144.204.65.4] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CpLN2-00050x-00; Thu, 13 Jan 2005 22:55:45 -0800 Received: from cc-mykerinos.onera (localhost [127.0.0.1]) by onera.onera.fr with ESMTP id j0E6tecW020789; Fri, 14 Jan 2005 07:55:42 +0100 (MET) Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426) id ED4612329C; Fri, 14 Jan 2005 07:09:52 +0100 (CET) Date: Fri, 14 Jan 2005 07:09:52 +0100 From: Christian Perrier <[EMAIL PROTECTED]> To: Pol Danilov <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#290373: Debian Installation Report Template Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> X-message-flag: Outlook is a good virus spreading tool. It can send mail, too. X-pot_a_miel: [EMAIL PROTECTED] User-Agent: Mutt/1.5.6+20040907i Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by onera.onera.fr id j0E6tecW020789 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: > One problem I had was getting my cordless USB mouse to work... I have > a "Fellowes Cordless Notebook Mini Optical Mouse". It might have > simply been faulty hardware because the problem resolved once I > switched the connection to a different USB port. But when plugged into > the "bad port"... It would say it detected a USB device on the port > but that it couldn't enable it and told me "check the cord" or > something. Kind of funny because there is no cord between the USB > access point and the mouse. This error message was really annoying > because it would print about every 30 seconds no matter what I had on > the screen! It printed itself all over the blue configuration screens, > etc so I couldn't see what I was doing. > http://www.fellowes.com/FellowesAssets/Images/Catalog/Resize300/99197.j= pg This sounds like kernel-generated messages we can't do much about. As, as you noted, this is highly probably a faulty hardware problem, it's probably better having something showing up at the screen...even messily. Given that this install report is a complete success report, I do as usual with successful install report=A0: I close the bug..:-) This does not of course mean you weren't right to report. Knowing the installations are correct is important for the d-i team. Many thanks for yourtime testing the Debian Installer and reporting your results. Have fun with your new Debian system!