I have this problem on the 2.6.18 series custom made as well or official 
Debian kernel.

This is for the amd64 arch.

It seems like all of these bugs since 2.6.16 are being merged but I cannot 
tell which is the active one (none seem closed but all refer to being 
merged.)

The only fix I can find is to manually remove the entry from 
dpkg /var/lib/dpkg/status and also to manually remove any config files (it 
looks like it get them in any case.)
-- 
David Broome

On Debian Linux Sid using KMail


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to