In Ubuntu 13.04 x64 with kernel 3.8, my flopy drive now works perfectly. The systems recognizes the drive and displays an icon fo it on the Unity Launcher. I can click on the icon and am able to view the contents of the disk.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/441835 Title: Clicking on floppy gives "no device media found" 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: Invalid 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: Won't Fix Status in “linux” source package in Karmic: Invalid Status in “udisks” source package in Karmic: Invalid Status in “udisks” package in Arch Linux: New Status in “udisks” package in Debian: Confirmed 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 manage notifications about this bug go to: https://bugs.launchpad.net/devicekit/+bug/441835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
