(In reply to comment #22) > (In reply to comment #21) > > What is the status here? Sister bug http://bugs.gentoo.org/338185 has been > > open > > for too long. > > It's not really something I'm planning to spend time on in udisks since a) I'm > focusing on udisks2; and b) floppies are extremely rare nowadays.
Also in Debian there are several reports regarding that issue. 561737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561737 561746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561746 592719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592719 596890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596890 622618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622618 669973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669973 Having a working udisks2 package will not be enough, since that one will not be ported back to already released distribution versions. I wonder if there are problems with RedHat or openSUSE too. Or do they ship an earlier version not affected by this regression. Anyway, it is known what caused the regression. So it would be great if the attached patch to this report – which has been tested – could be applied. The problem of systems having a delay during start up because no floppy drive is attached should be able to be fixed differently. Since the commit message of the commit causing the regression does not specify the root cause, I can only guess. Is the floppy module doing the probing or udev? If we figure that out people affected by a crappy BIOS should be able to pass in a command line option and be done with it. […] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441835 Title: Clicking on floppy gives "no device media found" To manage notifications about this bug go to: https://bugs.launchpad.net/devicekit/+bug/441835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
