This is the direct consequence for fixing floppies in the first place
(bug 441835). We have absolutely no way of poking the floppy controller
whether there is actually a floppy behind it, as this causes hard
freezes of about 20 seconds if there is none. Thus, we can either skip
floppies entirely
Good morning.I read in a earlier post that someone disabled the floppy
in their BIOS and Quantal stopped trying to mount the floppy.I just did
this and Quantal stopped trying to mount the floppy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Since this is appearing on purely physical machines (not just VMWare) -
it seems to be an issue with the way Ubuntu deals with what appears in
the BIOS.
I went into the VM machine's BIOS and [Disabled] the reference to the
[Disabled] the Floppy A. Now a Floppy no longer appears in the list
of
SlugiusRex [2012-11-21 0:09 -]:
Could it appear that somewhere during the upgrade from 12.04 to 12.10
the code was modified to enhance performance of the boot up process.
Not quite, but we switched from udisks to udisks2 which cleaned up the
device detection logic. udisks 1.x broke
