Double clicking on Floppy Drive gives an error (Unable to mount location) despite it's mounted but not opened in Hardy RC

This is part of the output I gat from running dmesg in the terminal.

[ 153.027117] floppy0: data CRC error: track 79, head 1, sector 18, size 2
[ 156.613116] floppy0: data CRC error: track 79, head 1, sector 18, size 2
[ 157.409991] floppy0: data CRC error: track 79, head 1, sector 18, size 2
[ 157.410011] end_request: I/O error, dev fd0, sector 2879
[ 157.410018] Buffer I/O error on device fd0, logical block 359

This is a known good FDD and disk. The drive was working to some extent in Hardy until hal was updated today. 3/24/08

The floppy drive problem appears to be with hal.

I confirm this bug in Ubuntu 8.04 beta 1 LiveCD

I also receive this error: "Unable to scan drive for media changes. Cannot invoke CheckForMedia on HAL (...) "

I also test:
sudo mount /dev/fd0 /mnt/
and It works good - I can read from floppy.

Early 8.04 alfa works good, but few last alfas 8.04 have errors with floppy.

Same problem here. Mounting it from the terminal works fine though.
Could this be an issue with GVFS?

I am able to mount the drive from the terminal but can not view any files.

 Nick B, are you able to view the files when you use the terminal to mount the drive?

Yes I was able to view the files on the floppy.
I also found out that the Disk Mounter applet for Gnome Panel will also mount the floppy without a problem.

I put it as gvfs bug, but I'm not sure.

In Hardy RC:

The FIRST time I try to mount floppy double clicking its icon I get the message you see in attachment.
In English sounds like:
"Unable to mount location"
"Unable to mount file"

but this doesn't prevent mounting itself because floppy is mounted correctly (just wait some seconds).
If I unmount and mount it again during the same gnome session no problem at all. (Apart from Bug #206860 and double folder opening bug)

The error message come up every FIRST mounting time of every session.

Very strange and bad looking for Hardy.

Putting "New" because I don't know if it's the right package.

Very strange. If you give it a few seconds it does actually mount the floppy despite the error. I don't recall this happening before though. There was an update for gnome-mount. I wonder if that has anything to do with it sort of working now.

So the error message could be a gnome-mount issue as well.

In fact when the error appear it only mounts floppy but it doesn't open it.

Clicking on Places->Floppy disk works correctly.

Clicking on Places->Floppy disk mount it correctly even if floppy is not opened.

I can confirm that:

1. The FIRST time you double-click on Computer->Floppy disk, you get an error message, but the floppy disk is mounted, although it's NOT opened in any Nautilus window. (This bug).

2. Clicking on Places->Floppy disk without a floppy in the drive, you DON'T get any error message. (Bug #206856).

3. When you unmount the mounted floppy disk (with right-click -> Unmount), the icon label don't go back to "Floppy Disk"; instead, it remains "1,5 MB Media". (Bug #206860).

Floppy disk support in GNOME 2.22 is definitely worse than GNOME 2.20.

@Sebastien

I saw you just reported Bug #206856 upstream and changed its Bug status.
Please give this bug an importance and a status too (reporting upstream if it needs)

the bug will be forwarded but the desktop team gets hundred bugs every week and the team working on those is pretty small so there is a limit to how much can done in a day, you are welcome to help and send the bug upstream if you think that things don't go quickly enough though

@Sebastien
Yes, I know the team is pretty small, I told you about that on purpose, because Bug #206856, #206860 and #203722 (this) have very similar context, so they could be dealt together, saving a lot of precious time.
If not, desktop team should take this bug some time in the future, restarting all work from the beginning.

The context doesn't make a difference there, it's just copying the description to bugzilla, there is no work to restart

Ok, I reported the bug upstream.

About work to restart, I meant that these bug could be patched together at once, if a person is aware of them.

Now it miss just the importance to be set (and status in case).

I'm running Hardy Heron X64 8.04
I also have this problem. If I double click on the floppy icon in Nautilus. The window titled 'Unable to mount location' is displayed with the message 'Can't mount file'.
If I click on OK in the message box I cannot access the disk (and any disk after that). If (after a reboot), instead, I ignore the message by closing it (top right X), the floppy disk drive can be accessed and is displayed as a 1.5MB Media disk. All files are available. If I then close Nautilus and unmount the floppy from the desktop, re-open Nautilus, try to open a new or the same floppy disk by double clicking on it, I do not get an error.
This may be related to the problem. I formatted another floppy using Gutsy and put some files on it a while ago. These included xorg.conf and menu.lst. When I try to open the disk in Nautilus I get the 'Unable to mount location' window followed by a new window titled 'Cannot mount volume' with the message 'Invalid mount option when attempting to mount the volume'. Unfortunately I have no means of checking the floppy at present.

Here are a few things I have noticed.

In Ubuntu Hardy I have all of the floppy drive problems mentioned in this thread.

In Xubuntu Hardy the same floppy drive and disk work as expected.

Both Ubuntu and Xubuntu use the same kernel and gvfs but Xubuntu uses Thunar as it's file manager. So, would the problem in Ubuntu Hardy be an issue with Nautilus?

same problem with cd-roms (exept audio disks), dvd and usbsticks.
manualy mounting works
 gnome-mount -vbd /dev/ etc also works
but by nautilus and double clicking gives an error: Unable to mount location / Can't mount file
see also 218834

working on a fully update Hardy version
does not open after seconds or minutes

This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=529547

I´m new to Ubuntu and have installed 8.04.1 on my Gigabyte MA790FX-DS5 / AMD 2.8 DC x86 and am having the same problems as listed above.

First time I put a new floppy in 8.04.1 it wouldn´t mount, despite the light being constantly on ? (tried access via Places / Computer). Next reboot it mounted and opened a window, but no matter what I did it wouldn´t unmount it cause it wasn´t mounted, despite the floppy light still being on.

forum thread here
http://ubuntuforums.org/showthread.php?t=858074

Following suggestion, I did a ´dmesg´ in terminal and have attached the resulting file to this report, hope it helps.

the gvfs task is enough there

upstream bug comment

"I don't have a floppy, so i can't test this. But it might be fixed by:

2009-03-05 Alexander Larsson <email address hidden>

        * monitor/hal/ghaldrive.c:
        * monitor/hal/ghalmount.c:
        * monitor/hal/ghalvolume.c:
        * monitor/hal/ghalvolumemonitor.c:
        Remove all locking (not needed since we're now
        a single threaded process).
        Don't emit signals in idle, thus risking callback
        reordering. We don't need this anymore as it was
        part of the locking structure.

        This should fix the "No mount object for mounted
        volume" error when mounting.

in gvfs 1.1.8.

Could someone test that?"

could somebody try on jaunty?

@Sebastien
Jaunty has gvfs 1.1.7 version now, so I can't test it until 1.1.8 will be available.

This may be related.
Using Jaunty Kubuntu kernel 2.6.28-8-generic #28-Ubuntu SMP Fri Mar 6 00:09:20 UTC 2009 x86_64 GNU/Linux. gvfs version 1.1.8-0ubuntu1.
Open Dolphin (version 1.2.1). Click on PC Floppy Drive (with floppy in drive). Get the error that the floppy is already mounted, but unable to view floppy files (see attached screenshot).

@Sebastien
Just tried Jaunty daily live cd with gvfs 1.1.8 and the bug isn't fixed unfortunately.

Please put it as "Triaged" again.

Thank you for bringing this bug to our attention. Unfortunately a paper cut should be a small usability issue that affects many people and is quick and easy to fix. I'm afraid this bug can't be addressed as part of this project.
A paper cut is a minor usability annoyance that an average user would encounter on his/her first day of using a new installation of Ubuntu 9.10

Hi

I have the same problem with 9.10 as well as CD ROm unmounting when you put in a Audio Disk. The CD reads data disks OK but the floppy reads no disks.

Hi

What do you mean by a minor paper cut. I canot read any Floppy disk on a fresh installation. What is the fix or troubleshooting steps I can take?

Status changed to 'Confirmed' because the bug affects multiple users.

code:
jirka@jirka-MS-7100:~$ dmesg |grep fd
[ 0.887727] Floppy drive(s): fd0 is 1.44M
[ 41.300056] end_request: I/O error, dev fd0, sector 0
[ 41.328049] end_request: I/O error, dev fd0, sector 0

May be bad drive.

My floppy drive works in 12.10 Alpha 1 live sesion, but #985680 still occured.

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/203722

This package has been removed from Ubuntu. Closing all related bugs.