This particular bug was fixed a day after beta release. The error
message does not appear any more. I tested it on a machine that does not
have a floppy drive, but I am going to test the issue on another machine
that has, and report back with the results.
--
Hardy: Unable to scan Floppy Drive
The floppy is working on today's (2008-03-25) daily snapshot live cd.
** Changed in: gvfs (Ubuntu)
Status: Triaged = Fix Released
--
Hardy: Unable to scan Floppy Drive for media changes
https://bugs.launchpad.net/bugs/197954
You received this bug notification because you are a member of
Sebastien: I am using a fully updated Hardy. It contains all the
updates, even the ones after Alpha 6. It is still doing the same error.
--
Hardy: Unable to scan Floppy Drive for media changes
https://bugs.launchpad.net/bugs/197954
You received this bug notification because you are a member of
I still get the issue.
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/12516373/Screenshot.png
--
Hardy: Unable to scan Floppy Drive for media changes
https://bugs.launchpad.net/bugs/197954
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Oh I forgot to say, that the error dialog also appears on a desktop
computer that doesn't even have a floppy drive. According to the GNOME
bug tracker, hal 0.5.10, which Hardy ships, doesn't contain this method.
--
Hardy: Unable to scan Floppy Drive for media changes
I don't have a floppy drive in my own computer, so I could not test it,
but something like this shell script could do the trick:
if [ `mount | grep /media/floppy0 | wc -l` -eq 0 ]
then
mount /media/floppy0 nautilus /media/floppy0
else
nautilus /media/floppy0
fi
Place this in
Please do something about this bug. I don't think it is that hard. It is
really hard to explain the method to open a document received on a
floppy for a first time user. Should I tell her to open the floppy,
close the error dialog, go back, open floppy again? She won't believe me
that Ubuntu is
