Your message dated Mon, 31 Jan 2011 11:47:16 +1100 with message-id <20110131004716.GW3684@hezmatt.org> and subject line Bug#381975: cannot undo ssid entry has caused the Debian Bug report #381975, regarding graphical-installer: cannot undo ssid entry 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.) -- 381975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381975 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: graphical-installer: cannot undo ssid entry
- From: Michael Gilbert <michael.s.gilbert@gmail.com>
- Date: Mon, 07 Aug 2006 22:34:28 -0400
- Message-id: <20060808023428.8820.83255.reportbug@slunk>
Package: debian-installer Severity: normal if one should mistakenly enter an incorrect ssid value in the graphical-installer wireless config, and press enter, one will not be able to undo the mistake. using the "go back" will not go to the ssid, but it will eventually go to the main d-i menu. however, even from there, it is not possible to get to the ssid config dialog. mike -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
- To: 381975-done@bugs.debian.org
- Subject: Bug#381975: cannot undo ssid entry
- From: Matthew Palmer <mpalmer@debian.org>
- Date: Mon, 31 Jan 2011 11:47:16 +1100
- Message-id: <20110131004716.GW3684@hezmatt.org>
I'm closing this bug, as I cannot reproduce it in a current installer release and requests for further information have gone unanswered. If you can still reproduce the problem in a current installer release, please reopen this bug with the necessary details to reproduce the problem. - Matt
--- End Message ---