registry team mailing list archive

[Nestor <nestor.esther@xxxxxxxxx>]

I use Ubuntu 10.10, 32-bit,  computer i.386

I mount the floppy with the command:

(suggested by Seppo Aarnio)

udisks --mount /dev/fd0

I Click on the icon that appears on the desktop screen,
it opens a blank window

I pick up any file (smaller that 1MB, example an image.jpg) and I drop it on
the blank window.(Or drop  it on the floppy icon)  It stay there.

Then I check it by openning it with gimp or an image viewer, and it
works.

I umount the floppy, take it out, put it back again, mount it

Then I check it by openning it with gimp or an image viewer, and it works
very well.

I can erase the file as a normal user.

I do all of this as user. Never as root.

Then to format the floppy, first I unmount it

second, I open a terminal and as root:

sudo mformat a:

and the floppy is formatted.
--------------------------------------------------

NOW the TEST, i use a live cd (ubuntu 10.10)....and I can read the floppy
content BUT I can NOT WRITE on it as normal user. I can write in it or erase
the files using sudo, like you wrote.

--------------------------------------------------

Probably the problem with the floppy recognition and function is the same
with the installed Ubuntu 10.10, I have to use a command new to the software
of Ubuntu 10.10 in order that the distro recognize the floppy. But for a
reason that I don't know the solution for the installed version does not
work 100% in the live installation. Maybe it is due to a partial install of
drivers in the live cd.

Sorry I can not help.



2010/11/10 Torkil Olesen <torkilo@xxxxxxxxxx>

> Floppy working in a live cd xubuntu 10.10
>
> I have tried xubuntu 10.10 from live cd and got a floppy icon on the
> desktop. It could be mounted, opened and I could read a file, but not write
> (only root permission).
> Later I have installed xubuntu desktop in an ubuntu 10.10 version. Here the
> floppy could not be mounted, and properties of the floppy drive says 8.9 GB
> free ???
> I think this gives one more hint about the bug, which Canonical has not
> been able to solve during more than a year.
>
> On the same Pc I have during a year used Poppy Linux 4.3.1., which
> starts from cd, works very fast from memory and have no problems with
> floppies.
>
> --
> Clicking on floppy gives "no device media found"
> https://bugs.launchpad.net/bugs/441835
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in obsolete project: Fix Released
> Status in GVFS: Unknown
> Status in The Linux Kernel: Invalid
> Status in udev - /dev/ management daemon: Invalid
> Status in abstraction for enumerating and managing block devices: Unknown
> Status in “devicekit-disks” package in Ubuntu: Invalid
> Status in “linux” package in Ubuntu: Invalid
> Status in “udisks” package in Ubuntu: Triaged
> Status in “devicekit-disks” source package in Lucid: Invalid
> Status in “linux” source package in Lucid: Invalid
> Status in “udisks” source package in Lucid: Triaged
> Status in “devicekit-disks” source package in Karmic: Triaged
> Status in “linux” source package in Karmic: Invalid
> Status in “udisks” source package in Karmic: Invalid
>
> Bug description:
> In Karmic GNOME, floppies are detected correctly by linux, udev,
> devkit-disks, and gvfs. However, when clicking on the floppy icon in GNOME,
> you get a "no medium found" error.
>
> Remote reproducer: gvfs-mount -li
>
>  - When you just start that with no other processes running, you get a
> correct "volume" for /dev/fd0 ("floppy0").
>  - When you start it through dbus-launch, you get a floppy0 "drive"
> instead, and no volume
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/devicekit/+bug/441835/+subscribe
>

-- 
Clicking on floppy gives "no device media found"
https://bugs.launchpad.net/bugs/441835
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for udev.