Bug#369212: marked as done (installation-report)
Your message dated Wed, 08 Sep 2010 03:58:13 +0000
with message-id <E1OtBnZ-0005Bl-UL@ravel.debian.org>
and subject line Closing old installation report #369212
has caused the Debian Bug report #369212,
regarding installation-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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
369212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369212
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Boot method: network
Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/
arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
ftp://ftp2.jp.debian.org/
Date: 2006/May/28
Machine: Sotec Winbook
Processor: Celeron 400MHz
Memory: 128MB
Partitions: /dev/hda1 ext3 4040000 2752768 1082004 72% /
Output of lspci and lspci -n:
lspci:
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03)
0000:00:02.0 VGA compatible controller: Neomagic Corporation NM2160 [MagicGraph 128XD] (rev 01)
0000:00:04.0 Multimedia audio controller: ESS Technology ES1968 Maestro 2
0000:00:06.0 Communication controller: Agere Systems 56k WinModem (rev 01)
0000:00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:00:0a.0 CardBus bridge: Texas Instruments PCI1221
0000:00:0a.1 CardBus bridge: Texas Instruments PCI1221
:lspci -n
0000:00:00.0 0600: 8086:7192 (rev 03)
0000:00:02.0 0300: 10c8:0004 (rev 01)
0000:00:04.0 0401: 125d:1968
0000:00:06.0 0780: 11c1:0440 (rev 01)
0000:00:07.0 0601: 8086:7110 (rev 02)
0000:00:07.1 0101: 8086:7111 (rev 01)
0000:00:07.2 0c03: 8086:7112 (rev 01)
0000:00:07.3 0680: 8086:7113 (rev 02)
0000:00:0a.0 0607: 104c:ac19
0000:00:0a.1 0607: 104c:ac19
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:
1. An error message was displayed while configureing foomatic (? I'm
not very sure) environment saying
*** glibc detected *** double free or corruption (!prev): 0x08179528 ***
2.The Installer abnormally stopped while configureing packages
(I suspect the contradictive files in manpages-ja and xmanpages-ja).
After continueing installation (Grub installation), the system can
boot normally. But, some packages may not be correctly installed/
configured. (At least, xmanpages-ja is required for Japanese
environment but not installed)
3. printconf command cannot access to foomatic DB (perhaps, because of
the same reason of error 1.). message is shown as
# printconf
*** glibc detected *** double free or corruption (!prev): 0x08179528 ***
Unable to read printer database. Please ensure the "foomatic-db" package is
installed properly.
Fortunately, my printer is a postscript printer, and I can set it up
using similar data in hplp database.
4.Time setting is incorrect. The installer seems to automatically
set the timezone to Tokyo/Japan, and using UTC setting. In result,
the time is set to 9 hours advance to JST.
--
KOYAMA Teruo
mail: koyama.t[at]b-star.ne.jp
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---
Reply to: