(In reply to comment #20) > > But I don't think this is related to the patch or udisks2. > > I see the same behavior with "mdir". After inserting a new disk, "mdir" > > fails with: > > Can't open /dev/fd0: No such device or address > > Cannot initialize 'A:' > > Running it a second time works. Also after running mdir once, "udisksctl > > mount" works and vice versa. So this rather seems to be a kernel issue I > > think. > > Same behaviour on kernel 3.14. > Floppy mounts from the first attempt on a kernel 3.2.
Thanks for testing. I couldn't reproduce the problem here, but I'll try with a newer kernel next week. Unfortunately I only have access to an actual floppy drive about once a week. BTW, what kind of distribution and destop environment are you two using? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313874 Title: fstab-based mounts not done as calling user To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1313874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
