Ubuntu

Clicking on floppy gives "no device media found"

Reported by Antec on 2009-10-03
584
This bug affects 124 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Undecided
Unassigned
gvfs
Unknown
Medium
obsolete
Fix Released
Medium
udev
Invalid
Undecided
Unassigned
udisks
Invalid
Medium
devicekit-disks (Ubuntu)
Medium
Unassigned
Nominated for Maverick by Chris Parker
Karmic
Medium
Ben Clevers
Lucid
Medium
Unassigned
linux (Ubuntu)
Medium
Andy Whitcroft
Nominated for Maverick by Chris Parker
Karmic
Undecided
Unassigned
Lucid
Medium
Andy Whitcroft
udisks (Arch Linux)
New
Undecided
Unassigned
udisks (Debian)
Confirmed
Unknown
udisks (Ubuntu)
High
Unassigned
Nominated for Maverick by Chris Parker
Karmic
High
Unassigned
Lucid
High
Unassigned

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

Related branches

Antec (info-janmob) wrote :

In bug 23309 we disabled partition table probing for floppy devices.

Unfortunately, the partition table prober is also used for determining if media is inserted by setting DKD_MEDIA_AVAILABLE.

So media detection on floppies is now broken.

We should move that detection elsewhere.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged

Hello, was it working in Jaunty?

FGTR4738 (knyuf56) wrote :

Yes, for me it was working perfectly in Jaunty. On the systems here as soon as I upgraded to Karmic it no longer worked from the pull down menus "Places." We're simply working around it by /media$ mount floppy

Sergio Zanchetta (primes2h) wrote :

== Regression details ==
Discovered in version: Karmic Koala 9.10
Last known good version: Jaunty Jackalope 9.04

tags: added: regression-release

Having the same problem in Kubuntu 9.10. 64-bit. Tried to format with Kfloppy 4.3.0, KDE 4.3.3, but I the message "Internal error: device not correctly defined".

wraithmonk wrote:
> Having the same problem in Kubuntu 9.10. 64-bit. Tried to format with
> Kfloppy 4.3.0, KDE 4.3.3, but I the message "Internal error: device not
> correctly defined".
>
>
I fwd this to Sergio, one of the experts at Ubuntu bugs who is working a
solution to this problem as while it is in two distros, I think it is
the same basic problem, and oversight on IDE or internal floppy perhaps
brought about by usb external floppies and many of he new small netbooks
not having a floppy..... That would be a guess on part...

I can reproduce the bug in 9.10 with a fresh install AMD 64bit and also on another system 32bit after upgrading from 9.04. In both cases this is with an internal 3.5in 1.44 floppy formatted MS-DOS

One can mount the floppy by using the command:
sudo mount /dev/fd0 /media/floppy0 -o umask=000

I also tried changing the floppy line in /etc/fstab to:
/dev/fd0 /media/floppy0 vfat defaults,users,noauto,umask=000 0 2
and it was no help. This is the same as for a working 9.04 system

Antec (info-janmob) wrote :

I wonder if grub2 boot-reloader miss floppy module in the right way already on boot? And i don't see the floppy at all in /etc/fstab or /etc/mtab, but the green diod on yhe floppy blink when the computer boot.

Antec wrote:
> I wonder if grub2 boot-reloader miss floppy module in the right way
> already on boot? And i don't see the floppy at all in /etc/fstab or
> /etc/mtab, but the green diod on yhe floppy blink when the computer
> boot.
>
>
I don't know what the developers did on this one. I sent in the bug
report. From what I can tell they just left out the software that makes
a internal floppy work. Someone at Ubuntu wrote: that internal floppy's
are "rare" clearly they must having been thinking 10" notebook and USB
and not about the hundreds of millions of computers that still have and
use a floppy. Even if the "floppy" is added into fstab and modules it
still does not work. The expert at first started out on it, but I think
he gave up, and for us we are not going to upgrade to 9.10 and will keep
using 8.10 and 9.04. (*8.10 works really good and has been flawless)
Hopefully they will put in a fix that will go in an update. I kind of
get the feeling that the reason that 9.10 boots so fast is because it is
not really doing a proper look to see what "plug and play" is in the
system but that is just a guess, one thing for sure they did cut a
corner and that was a floppy. It could be related to IDE but they will
have to figure it out. Everytime I send in another bug on it I get a
letter back about no new bugs so for now I just kind of gave up, as only
one of our computers have the problem with 9.10 the others with 8.04 all
work fine. I guess a lot of people will be changing back to 9.04 or
8.10 if they don't fix it. Millions of people still use floppy.

The company i work on have 103 Ubuntu computers and 80 of them are Ubuntu 8.04 LTS the rest is 9.04. We have four to test the new Ubuntu 9.10. If the 9.10 not work properly can we not upgrade any more computers and we must wait and look on next LTS version and test them very hard. OpenSUSE 11,2 have also problems with floppydrive there not working ether .

This code is working like Francisco Canabas wrote but a new floppy module is started between the standard floppy module? In case no other alternative are availability.

sudo mount /dev/fd0 /media/floppy0 -o umask=000

Sergio Zanchetta (primes2h) wrote :

Giving
gvfs-mount -d /dev/fd0

Sergio Zanchetta (primes2h) wrote :

Giving
sudo gvfs-mount -d /dev/fd0

Sergio Zanchetta (primes2h) wrote :

ls -l /dev/fd0

Sergio Zanchetta (primes2h) wrote :

dmesg (after mounting with 'sudo gvfs-mount etc.')

Sergio Zanchetta (primes2h) wrote :

udev log

Andy Whitcroft (apw) wrote :

As the device is seen by udev and correctly created during the early boot it does not seem to be a bug in the kernel. It may be a permissions issue with the fd drive device as made by udev, or alternatively an issue at a higher level:

  KERNEL[1258912797.217841] add /devices/platform/floppy.0/block/fd0 (block)
  UDEV_LOG=3
  ACTION=add
  DEVPATH=/devices/platform/floppy.0/block/fd0
  SUBSYSTEM=block
  DEVNAME=fd0
  DEVTYPE=disk
  SEQNUM=1006
  MAJOR=2
  MINOR=0

Will add tasks for those levels for confirmation.

Andy Whitcroft (apw) wrote :

The device seems to be being detected correctly and udev informed as we do get a /dev/fd0. So it seems either the device does not have appropriate permissions, or the notification not being passed on to higher layers, or indeed those layers may not be taking appropriate action. Therefore adding tasks for udev and for gvfs to see if they can detemine why. Logs are below for the udev components.

Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: Triaged → Invalid

Antec wrote:
> The company i work on have 103 Ubuntu computers and 80 of them are
> Ubuntu 8.04 LTS the rest is 9.04. We have four to test the new Ubuntu
> 9.10. If the 9.10 not work properly can we not upgrade any more
> computers and we must wait and look on next LTS version and test them
> very hard. OpenSUSE 11,2 have also problems with floppydrive there not
> working ether .
>
> This code is working like Francisco Canabas wrote but a new floppy
> module is started between the standard floppy module? In case no other
> alternative are availability.
>
> sudo mount /dev/fd0 /media/floppy0 -o umask=000
>
>
We have 9.04 and 8.04 LTS, did not like 8.10 for some reason I recall it
had prolbems too.
However 9.04 worked fine and I think what we will do is put it back onto
the hard drive with 9.10 and just stop using 9.10 for a while.
Apart from the Open Office versions being different that has not much
effect on functionality as both work fine and I kind of think the older
one that is still using firefox 3.0.15 and google chrome as we kept the
old firefox and did not let it update to 3.5, and it has the new chrome
it kind of seems more stable and faster once it is up and running. So
there is a lot to be said that is good about 8.04 and 9.04. 9.10
otherwise is pretty good, but I think up and running 9.04 is a better
program and 8.04 is far more stable and proven dependable.

John (invent-write) wrote :

Andy Whitcroft wrote:
> The device seems to be being detected correctly and udev informed as we
> do get a /dev/fd0. So it seems either the device does not have
> appropriate permissions, or the notification not being passed on to
> higher layers, or indeed those layers may not be taking appropriate
> action. Therefore adding tasks for udev and for gvfs to see if they can
> detemine why. Logs are below for the udev components.
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Invalid
>
> ** Changed in: linux (Ubuntu)
> Assignee: (unassigned) => Andy Whitcroft (apw)
>
>
I think the layers that would do something are just not in there to do
it. I think they did USB support and forgot about floppy by ribbon cable
as an internal device.
I think the developers were thinking more NOTEBOOK and less about
desktop and older laptops.

John (invent-write) wrote :

Andy Whitcroft wrote:
> As the device is seen by udev and correctly created during the early
> boot it does not seem to be a bug in the kernel. It may be a
> permissions issue with the fd drive device as made by udev, or
> alternatively an issue at a higher level:
>
> KERNEL[1258912797.217841] add /devices/platform/floppy.0/block/fd0 (block)
> UDEV_LOG=3
> ACTION=add
> DEVPATH=/devices/platform/floppy.0/block/fd0
> SUBSYSTEM=block
> DEVNAME=fd0
> DEVTYPE=disk
> SEQNUM=1006
> MAJOR=2
> MINOR=0
>
> Will add tasks for those levels for confirmation.
>
> ** Also affects: gvfs (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Also affects: udev (Ubuntu)
> Importance: Undecided
> Status: New
>
>
What I did not try but it might work is get the program titled "floppy"
out of the older 9.04 repository and see if it will load in 9.10 As
9.10 does not have that in it's repository, and the previous versions did.

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
Changed in udev (Ubuntu):
importance: Undecided → Medium

The attached udev log shows that a device was created

Changed in udev (Ubuntu):
status: New → Invalid

Scott James Remnant wrote:
> The attached udev log shows that a device was created
>
> ** Changed in: udev (Ubuntu)
> Status: New => Invalid
>
>
I don't know anything about how it was made, I just know it don't work,
so we will keep using older versions until it is fixed on the rest of
the computers and at some point be adding an older version to this one
so the floppy can be used. The necessary software to use or read a
floppy is not in Ubuntu 9.10.

They just left out the necessary software that is needed to utilize an internal floppy and until it is fixed we will just keep using older versions that do work. I don't think it is a bug, I think it is an oversight that was just left out, by people thinking small notebook and USB and not about the millions of laptops and desktops that do have internal FLOPPY. Someone just has to go back, add that in and then let it go out in an update.

I just want to comment, that my floppy drive works well in an updated version of 9.04 to 9.10, but it does not work from the common GUI interface.

See my description in Bug #485684

Sebastien Bacher (seb128) wrote :

the duplicate bug mentioned in recent comments indicate the devicekit-disks interface has issues with the floppy drive too, seems rather a bug in devicekit-disks there

affects: gvfs (Ubuntu) → devicekit-disks (Ubuntu)
Sergio Zanchetta (primes2h) wrote :

This bug affects Lucid Lynx too.
For more info and logs see duplicate bug #475500.

Could someone open two task against Karmic and Lucid respectively, please?

Due to the fact that this seems to affect a quite large number of users I mark it with "high" importance.
There are countries in which floppy is still a common device and there are still people having old archives in floppies using quite old hardware.
There are also other bug reports I'm investigating into, candidate as duplicate of this one.

Changed in devicekit-disks (Ubuntu):
importance: Medium → High
Antec (info-janmob) wrote :

Thanks Sergio Zanchetta, this bugs is in level high and i think so myself.

 More and more Linux users are dropping microsoft alltogether and using
Linux as a stand-alone OS and needing basic functions to read and write
files on media such as 'floppy'. For some time Linux has been going from
a secondary OS to a solitary OS in its usage. floppy is an important
function to have, especially with text files and data.

"More and more Linux users are dropping microsoft alltogether and using
Linux as a stand-alone OS and needing basic functions to read and write
files on media such as 'floppy'. For some time Linux has been going from
a secondary OS to a solitary OS in its usage. floppy is an important
function to have, especially with text files and data. (posted by John)."

We have the same situation here in that we use quality cameras that have the floppy disk drive built in... they
are used for quick one-picture shots and using a floppy disk is ideal. The cameras are too expensive an
investment to dump them to use Ubuntu, so, this fix is vital for us too. We agree too, there are millions still
using floppy disks for a host of reasons. It has nothing to do with using the latest equipment, we still
install floppy drives for our specific requirements. They are ideal for short text files and numerous convenient temporary portable archives of information.

Martin Pitt (pitti) wrote :

From the udev side, everything seems to be okay. Sergios' dmesg has

[80538.492091] end_request: I/O error, dev fd0, sector 0
[81237.645087] floppy0: data CRC error: track 5, head 0, sector 2, size 2
[81237.845784] floppy0: data CRC error: track 5, head 0, sector 2, size 2

which looks slightly disturbing, but it could be a side-effect of probing.

Can you please do

  devkit-disks --dump > /tmp/dk-disks.txt

and attach /tmp/dk-disks.txt here? After that, please do

  devkit-disks --monitor-detail > /tmp/dk-disks.log

then insert a floppy, try to mount it in GNOME (do you have an icon for it?), then press Control-C, and attach /tmp/dk-disks.log, too.

Changed in devicekit-disks (Ubuntu):
status: New → Incomplete
Sergio Zanchetta (primes2h) wrote :
Sergio Zanchetta (primes2h) wrote :
Sergio Zanchetta (primes2h) wrote :

I have a icon for floppy (both in Places and in 'Computer' folder).
There is just one difference, double click from the folder gives me "Unable to mount" "no device media found", clicking on Places->Floppy don't give me any information.
In both cases I get the same log from
devkit-disks --monitor-detail

John Higby (jhhigby) on 2009-11-25
Changed in linux (Ubuntu):
status: Invalid → Confirmed
Martin Pitt (pitti) wrote :

Thanks. So dk-d knows about it, but does not know about the file system on the device.

Does "devkit-disks --mount /dev/fd0" work?

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Martin Pitt (pitti) wrote :

So part of the problem would be that 60-persistent-storage.rules doesn't probe for file systems on floppy devices.

I suppose devkit-disks --mount says "Not a mountable file system"?

1 comments hidden view all 692 comments
Martin Pitt (pitti) wrote :

Could anyone try this: In /lib/udev/rules.d/60-persistent-storage.rules, change

  KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*", GOTO="persistent_storage_end"

to not have the "fd*" in it, i. e.

  KERNEL=="mtd*|nbd*|gnbd*|btibm*|dm-*|md*", GOTO="persistent_storage_end"

Then udev should probe the floppy on the change event initiated by the mount call (dk-disk's DrivePollMedia()).

Martin Pitt (pitti) wrote :

Could anyone try this: In /lib/udev/rules.d/60-persistent-storage.rules, change

  KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*", GOTO="persistent_storage_end"

to not have the "fd*" in it, i. e.

  KERNEL=="mtd*|nbd*|gnbd*|btibm*|dm-*|md*", GOTO="persistent_storage_end"

Then udev should probe the floppy on the change event initiated by the mount call (dk-disk's DrivePollMedia()).

summary: - [Karmic] floppy is not working (Ubuntu 9.10)
+ [Karmic] floppy is not working

It shouldn't be retrofitted into the normal persistent storage rules like that, because we don't have media detection for floppies - and you don't want the usual persistent symlinks for them anyway even if they did.

Basically you really just want blkid run on it - if we have a "floppy present" signal from dk-disk, then we could do it on a special "change" rule?

Martin Pitt (pitti) on 2009-12-14
Changed in linux (Ubuntu Karmic):
status: New → Invalid
Changed in udev (Ubuntu Karmic):
status: New → Invalid
Martin Pitt (pitti) on 2009-12-14
affects: devicekit-disks (Ubuntu Karmic) → gvfs (Ubuntu Karmic)
Changed in gvfs (Ubuntu Karmic):
status: New → Incomplete
description: updated
tags: added: regression-potential
summary: - [Karmic] floppy is not working
+ [Karmic] clicking on floppy gives "no device media found"
Martin Pitt (pitti) on 2009-12-14
description: updated
Martin Pitt (pitti) on 2009-12-14
Changed in gvfs (Ubuntu Karmic):
status: Incomplete → Triaged
Changed in gvfs (Ubuntu Lucid):
status: Incomplete → Triaged
Martin Pitt (pitti) on 2009-12-14
affects: gvfs (Ubuntu Karmic) → devicekit-disks (Ubuntu Karmic)
Changed in devicekit:
status: Unknown → Confirmed
summary: - [Karmic] clicking on floppy gives "no device media found"
+ Clicking on floppy gives "no device media found"
Changed in devicekit-disks (Ubuntu Karmic):
importance: Undecided → High
Martin Pitt (pitti) on 2010-02-15
affects: devicekit-disks (Ubuntu Karmic) → udisks (Ubuntu Karmic)
Changed in devicekit:
importance: Unknown → Undecided
status: Confirmed → New
importance: Undecided → Unknown
status: New → Unknown
Changed in devicekit:
status: Unknown → Confirmed
Changed in devicekit:
status: Confirmed → Fix Released
Martin Pitt (pitti) on 2010-03-01
affects: udev (Ubuntu Karmic) → devicekit-disks (Ubuntu Karmic)
Changed in devicekit-disks (Ubuntu Karmic):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: Invalid → In Progress
Changed in udisks (Ubuntu Karmic):
status: Triaged → Invalid
Changed in udisks (Ubuntu Lucid):
assignee: nobody → Martin Pitt (pitti)
status: Triaged → Fix Committed
Martin Pitt (pitti) on 2010-03-01
tags: removed: regression-potential
Changed in udisks (Ubuntu Lucid):
status: Fix Committed → Fix Released
Martin Pitt (pitti) on 2010-03-01
summary: - Clicking on floppy gives "no device media found"
+ Mounting floppies does not work
Changed in devicekit-disks (Ubuntu Karmic):
status: In Progress → Triaged
Martin Pitt (pitti) on 2010-03-01
Changed in udisks (Ubuntu Lucid):
status: Fix Released → Triaged
Martin Pitt (pitti) on 2010-03-01
summary: - Mounting floppies does not work
+ Clicking on floppy gives "no device media found"
Changed in devicekit-disks (Ubuntu Karmic):
assignee: Martin Pitt (pitti) → nobody
Changed in udisks (Ubuntu Lucid):
status: Triaged → Fix Released
Changed in udisks (Ubuntu Lucid):
status: Fix Released → Incomplete
Changed in devicekit-disks (Ubuntu Karmic):
assignee: nobody → Ben Clevers (clevers-ben)
Martin Pitt (pitti) on 2010-09-01
Changed in udisks (Ubuntu Lucid):
assignee: Martin Pitt (pitti) → nobody
status: Incomplete → Triaged
Changed in udisks (Ubuntu):
status: Fix Released → Triaged
Changed in devicekit:
importance: Unknown → Medium
Changed in gvfs:
importance: Unknown → Medium
tags: added: maverick
Changed in udev:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Changed in linux:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Changed in udisks:
status: Unknown → Confirmed
Changed in devicekit:
importance: Medium → Unknown
Changed in devicekit:
importance: Unknown → Medium
Changed in udisks:
importance: Unknown → Medium
Gary M (garym) on 2011-02-09
tags: added: karmic lucid natty
Changed in udisks (Debian):
status: Unknown → Confirmed
Martin Pitt (pitti) on 2011-04-10
Changed in udisks (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
Martin Pitt (pitti) on 2012-04-27
Changed in devicekit-disks (Ubuntu Karmic):
status: Triaged → Won't Fix
Aiman Baharna (aiman) on 2012-06-09
no longer affects: lucid
612 comments hidden view all 692 comments
Ubuntu QA Website (ubuntuqa) wrote :

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

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

1 comments hidden view all 692 comments

On 6/10/2012 10:15, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:20, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:25, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:30, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:35, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:40, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:45, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:50, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

G. R. Main (grmain) wrote :

On 6/10/2012 10:55, Ubuntu QA Website wrote:
> This bug has been reported on the Ubuntu ISO testing tracker.
>
> A list of all reports related to this bug can be found here:
> http://iso.qa.ubuntu.com/qatracker/reports/bugs/441835
>

Ubuntu QA Website (ubuntuqa) wrote :

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

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

tags: added: iso-testing
1 comments hidden view all 692 comments
NoOp (glgxg) wrote :

Unsubscribing due to spamming from QA ISO testing/QA Website.

bert07 (marien.bert) wrote :

@ Martin.

Alas I am a too "small" a Linux user to test-drive this.

I can only report.

Sorry.

This still affects me in 12.04LTS.

Even if floppies are rare on the general desktop, I would sure like to see this fixed. Floppies still have a strong niche in specialty equipment. I have a bunch of machines here with floppy drives.

Is there a work-around? Older version that works? Udisks2? Other?

One workaround is using this command (as normal user)
udisks --mount /dev/fd0
to mount a floppy, then it can be safely detached via GUI (e.g. in
nautilus, right click the floppy icon...).
Once can create a .desktop file to run the command and drag&drop it onto
the unity launcher.

Hope this helps.

Cheers,
   T

OK, long time without an update. In the mean time development focus has been udisks 2.0 which is a completely different codebase where floppy disks actually work. Since udisks 2.0 has been shipping in distros since the spring, I'm not really interested in fixing this for udisks 1.x. So I'm closing it as WORKSFORME. Apologies if this is inconvenient for you but please do update to the latest version. Thanks!

Changed in udisks:
status: Confirmed → Invalid

Excellent!!!

Larry
---
*Laurence Nagel*
*Omega Enterprises Consulting*
*251 Stanford Avenue*
*Kensington, CA 94708*

*(510) 558-0842*
*<email address hidden>*
*http://www.omega-enterprises.net*

On 9/28/2012 11:40 AM, Zeuthen wrote:
> OK, long time without an update. In the mean time development focus has
> been udisks 2.0 which is a completely different codebase where floppy
> disks actually work. Since udisks 2.0 has been shipping in distros since
> the spring, I'm not really interested in fixing this for udisks 1.x. So
> I'm closing it as WORKSFORME. Apologies if this is inconvenient for you
> but please do update to the latest version. Thanks!
>

peter b (b1pete) wrote :

any idea when udisks2 will be available in 1204 ?

1 comments hidden view all 692 comments
Martin Pitt (pitti) wrote :

peter, it won't. Ubuntu 12.04 uses udisks 1.x

1 comments hidden view all 692 comments

Tagging this as WORKFORME is not acceptable and simply not true.
Ubuntu 10.04 is LTS and use this non working version of udisk.
12.04 is LTS too and also use this piece of crap that is the last 1.x version.

Some might consider beyond them as to why some people still use floppies but they do : in the professional world, a lot of appliances, industrial equipments rely on floppies, like machinetools...
Overlooking floppies as not worth a debug is despising at best, irresponsible at worst.
Please fix ASAP or cancel officially your last 1.x version so that the former and working version (1.0.1-1build1) is not replaced by this buggy one on our Ubuntu's.

Assuming Atlant's patch in comment 12 doesn't reintroduce the "long hangs on probing non-existant floppy drives" bug (which I've not managed to test myself as I couldn't reproduce the original problem), couldn't Atlant's patch be applied and be done with it? Or are the two bugs mutually unfixable?

(In reply to comment #27)
> Tagging this as WORKFORME is not acceptable and simply not true.
> Ubuntu 10.04 is LTS and use this non working version of udisk.
> 12.04 is LTS too and also use this piece of crap that is the last 1.x
> version.
>
> Some might consider beyond them as to why some people still use floppies but
> they do : in the professional world, a lot of appliances, industrial
> equipments rely on floppies, like machinetools...
> Overlooking floppies as not worth a debug is despising at best,
> irresponsible at worst.
> Please fix ASAP or cancel officially your last 1.x version so that the
> former and working version (1.0.1-1build1) is not replaced by this buggy one
> on our Ubuntu's.

I'm sorry that you are unhappy about Ubuntu but that's not my problem. As I said, udisks upstream - as well as many downstream distributors of our software - have moved on to udisks 2.x. I'm also sorry you are not happy to learn that your problem is fixed in the latest version.

To put it very bluntly, we don't care much about udisks 1.x anymore (we especially don't often listen to people calling it a "piece of crap") and we don't work much on it except for security bug-fixes. Because of this, we don't want our bug database to be littered with bugs that are never going to get fixed. So I'm closing this bug again. Don't reopen it or you will get banned.

(In reply to comment #29)
> To put it very bluntly, we don't care much about udisks 1.x anymore (we
> especially don't often listen to people calling it a "piece of crap") and we
> don't work much on it except for security bug-fixes. Because of this, we
> don't want our bug database to be littered with bugs that are never going to
> get fixed. So I'm closing this bug again. Don't reopen it or you will get
> banned.

Perhaps it should be resolved as WONTFIX rather than WORKSFORME in that case?

(In reply to comment #30)
> Perhaps it should be resolved as WONTFIX rather than WORKSFORME in that case?

If the issue wasn't fixed in 2.x and it's not an issue that I wanted to fix I would have closed it WONTFIX. If the issue was fixed in response to the bug, I'd close it with resolution FIXED. But since the issue is already an non-issue in the latest version, I chose to close it WORKSFORME. At least that's how I use Bugzilla. Other maintainers may use it in different ways.

bert07 (marien.bert) wrote :

I do not agree with the choice of words from 'Wintermute', but I do agree that I fix should be released for the LTS.

I know that this won't happen, but why not release the old udisks on the LTS.

Under Lucid (LTS) one could downgrade udisks so it kept working.
So why not dowwngrade udisks for the current LTS?

3 comments hidden view all 692 comments
bert07 (marien.bert) wrote :

I do not agree with the choice of words from 'Wintermute', but I do agree that I fix should be released for the LTS.

I know that this won't happen, but why not release the old udisks on the LTS.

Under Lucid (LTS) one could downgrade udisks so it kept working.
So why not downgrade udisks for the current LTS?

I do not agree with the choice of words from 'Wintermute', but I do
agree that I fix should be released for the LTS.

I know that this won't happen, but why not release the old udisks on the
LTS.

Under Lucid (LTS) one could downgrade udisks so it kept working.
So why not downgrade udisks for the current LTS?

On 15/11/2012 12:00, Wintermute wrote:
> Tagging this as WORKFORME is not acceptable and simply not true.
> Ubuntu 10.04 is LTS and use this non working version of udisk.
> 12.04 is LTS too and also use this piece of crap that is the last 1.x version.
>
> Some might consider beyond them as to why some people still use floppies but they do : in the professional world, a lot of appliances, industrial equipments rely on floppies, like machinetools...
> Overlooking floppies as not worth a debug is despising at best, irresponsible at worst.
> Please fix ASAP or cancel officially your last 1.x version so that the former and working version (1.0.1-1build1) is not replaced by this buggy one on our Ubuntu's.
>

bert07 (marien.bert) wrote :

Acceptaable or not, that won't help nobody.

We just should make it work.

Under Lucid we could make it work by downgrading.

And I agree that many people still use floppys (I'm one of them) but it does not help anyone when you start making noise.

bert07 (marien.bert) wrote :

BTW.

Did you read what Zeuthen wrote?

You might be banned.

And then what, will your floppy work then.

bert07 (marien.bert) wrote :

BTW2

It is not an UBUNTU thingy, it is a Linuw thing.
You won't get your floppy to work on Fedora are any other distro either.
Exept for Puppy. At least the former ones.

Though I must say that Udisks2 is not really what I what we (I) expected.
It keeps my floppy occupied al the time, so also there a fix is needed.

But Udisks2 seems to work. (more or less)

Do not forget that this is Linux, and they have to write everything (almost everything) from scratch.

Linux had come this far...

And it will go on developing. Making your and mine floppy work if given time.

PJSingh5000 (pjsingh5000) wrote :

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.

jglen490 (jglen490) wrote :

It's a darn shame that "the powers that be" don't care to fix something that is still of a great deal of importance to a few hundred thousand people - *buntu users. I recently added a floppy drive to my machine. It didn't work, but I just figured there was some package that didn't get loaded. So I found what I could with the fdutils package, and eventually found a workaround including a requirement for manual (menu select) mount and manual (menu select) umount, thanks to helpful users in kubuntuforums.net.

I'm using Kubuntu 12.04 - which is a LTS release - and, yes, direct support for floppy drives is lacking. I realize that someone, apparently having a great deal of power, would rather say WORKFORME than to offer up a solution that might actually help those who otherwise like and enjoy the (alleged) stability and utility of a long term support Linux distro. At least an answer of WONTFIX would have been an honest, as well as consistent answer.

I'm glad it works in PJSingh5000's platform, and I look forward to a later Kubuntu LTS that actually works the way that Kubuntu used to work before floppies were randomly pushed aside. And that WORKS FOR ME. Thank you.

Displaying first 40 and last 40 comments. View all 692 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.