GNOME Bugzilla – Bug 141049
Cannot Unmount Floppy Diskette
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gnome-applets Severity: normal Version: GNOME2.4.0 2.4.0 Gnome-Distributor: GNOME.Org Synopsis: Cannot Unmount Floppy Diskette Bugzilla-Product: gnome-applets Bugzilla-Component: drivemount Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When a floppy disk was mounted, and then modified and translated a document, from microsoft excel, to open office, then saved as an open office document, then open office was closed down, and tried to 'unmount' the diskette. However unmount is not a valid command, and eject reports "cannot open or read drive." Steps to reproduce the crash: 1. Insert Floppy Disk with excel document 2. Mount floppy. 3. Open the file with Open Office. 4. Print Document. 5. Save as Open Office Document. 6. Save as PDF File 7. in run line: unmount floppy. --Error: Unmount not valid command. 8. Eject Floppy. --Error: Cannot read or open drive. 9. go into terminal to unmount floppy. ---Error Again: Not valid command 10. in terminal eject floppy --Error: Cannot read or open device. 11. Type "Exit" in the terminal. (It exits but shortly thereafter a fatal error occurs) Expected Results: I expected it to, as with the eariler versions of linux that I've used, to have it rewrite the disk containing the new files and then have it unmounted as a part of the file system, indicating the the unmount / eject was sucessful. How often does this happen? Twice in the first few weeks I've used FADORA. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x006d7c32 in ?? ()
+ Trace 46381
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-25 12:47 ------- Unknown version 2.4.0 in product gnome-applets. Setting version to "1.0.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-applets". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was crimsonblade@excite.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
simpler steps to reproduce: 1. mount floppy with nautilus (i'm using 2.4.x) 2. open, modify, or save a file to the floppy with openoffice. 3. (optional) close open office 4. attempt to unmount disk, given error: "Nautilus was unable to unmount the selected volume." and when i clicked the "details" button, "umount: /floppy: device is busy umount: /floppy: device is busy" the only way i can figure out to get around this problem is to reboot the computer.
It sounds like if a program is opening something that is in /floppy. Could you try to do 'lsof /floppy' and see what keeps the floppy open ? Thanks!
i'll try that tonight when i go back home. i did find that when i killed nautilus, i was able to unmount the disk.
I've seen something about nautilus holding dirs open, you might want to upgrade to gnome 2.6.
# lsof /floppy COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME famd 420 josiah 41r DIR 2,0 7168 1 /floppy # When I killed famd, I was able to unmount the disk. In case it matters, the computers on which I'm having this problem are i386 and i686, Debian testing and unstable.
Could you use the command lsof -p PID replacing "PID" by the process ID of famd ? This may be a dup of bug 146420.
In spirit, it's a dup of bug 94552. *** This bug has been marked as a duplicate of 94552 ***