Package: hw-detect
Severity: important
Tags: d-i
This has been discussed on IRC earlier, but deserves a bug report so we
won't forget it before it's fixed :-)
If one first runs a module that fails (for instance, install LILO on a
non-existant drive, or install base from network with cable unplugged)
and then run hw-detect, weird stuff happens:
What actually happens is that hw-detect at some point sets
debconf/priority to "". This confuses main-menu profoundly -- current
version from sid manages to set pri=4, which is one step _higher_ than
critical, calling it "debian-installer/generic_error" of all things.
(main-menu from CVS fixes this issue, and sets pri=1, that is, "medium"
instead). Even better, right after that, one can spot
--> GET debconf/priority GET debconf/priority
<-- 20 Incorrent number of arguments
in the syslog; the origins of the double GET are rather unclear.
What, amazingly, solves the problem is to remove /etc/init.d/pcmcia-cs,
touching it instead to create an empty file. hw-detect runs the
following code fragment in postinst:
# avoid debconf daemon issues..
db_stop
/etc/init.d/pcmcia start </dev/null 2>&1 | logger -t hw-detect
which _seems_ innocent enough, but appearently is the source of the problems.
This should probably be investigated further. :-)
-- System Information:
Debian Release:
Architecture: i386
Kernel: Linux trofast.sesse.net 2.4.23-pre9 #2 Wed Nov 5 17:10:54 CET 2003 i686
Locale: LANG=C, LC_CTYPE=en_US.ISO8859-1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
