I had a similar issue a few months ago with the mysql package being in a "very bad inconsistent state", and with no apparent way of either uninstalling or fixing the package. If you do a Google search for 'mysql debian "Package is in a very bad inconsistent state"' you will find a number of others whom this has affected.
The solution that worked for me is the one found in the first comment here - www.debianhelp.org/node/1962 - of setting the RUNLEVEL initialisation variable at start-up. I mention this in case it helps track down/reproduce the problem. It seems the problem may also be related to splashy, unless I have misunderstood what the commenter in that thread is saying. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
