Description of problem: I transferred a song to my cell phone after trying out the newest obexd from updates-testing to comment in bodhi. After the song successfully transferred without corruption, i went ahead to unmount my external USB hard drive (where the song was). Now it wont let me. Version-Release number of selected component (if applicable): [root@localhost ~]# rpm -q obexd obexd-0.19-2.fc12.x86_64 How reproducible: transfer a file using the "sendto" option using Bluetooth from an external USB hard drive. unmount the hard drive once transfer compeltes Steps to Reproduce: 1.open /media/$USB_HARD_DRIVE in nautilus 2.transfer a file using bluetooth (right click-> send to) 3.let transfer complete 4.try to unmount the $USB_HARD_DRIVE Actual results: fails to unmount, screen shot of error window attached Expected results: should unmount normally without failure Additional info: [root@localhost ~]# umount /media/Ankur\ Backup/ umount: /media/Ankur Backup: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
Created attachment 399291 [details] screen shot -> unmount error clicking "unmount anyway" just brings the same error dialog box back up.
hi, i killed obex-client from the terminal using ps aux | grep obex kill "pid" Then i could unmount my hard drive normally. Ankur
What's the output of "lsof | grep /mount/point"? Which file is still used on the hard disk when the problem happens?
hey, [Ankur1@localhost torrents]$ lsof | grep /media/Ankur\ Backup/ obex-clie 8903 Ankur1 7r REG 8,17 7342973 3285622 /media/Ankur Backup/Music/Discographies/Blue Oyster Cult - Complete Discography 1972-2002/1994 - Cult Classic/01 Don't Fear The Reaper.mp3 [Ankur1@localhost torrents]$ ps aux | grep obex Ankur1 8903 0.1 0.1 21916 1228 ? S 18:34 0:00 /usr/libexec/obex-client regards, Ankur
(In reply to comment #4) > hey, > > [Ankur1@localhost torrents]$ lsof | grep /media/Ankur\ Backup/ > obex-clie 8903 Ankur1 7r REG 8,17 7342973 3285622 > /media/Ankur Backup/Music/Discographies/Blue Oyster Cult - Complete Discography > 1972-2002/1994 - Cult Classic/01 Don't Fear The Reaper.mp3 > Just clarifying, thats the file I just transferred to my phone. > > regards, > Ankur
*** Bug 622092 has been marked as a duplicate of this bug. ***
Still a bug in F13. File handles for files sent over bluetooth (via NetworkManager then obex-client) are kept open after the xfer is comlete, which means you can't remove the source media, or, in my case, nuke the parent directory of the file, until you manually kill the obex-client pid.
Still reproducible in : [Ankur@070905042 ~]$ rpm -q obexd obexd-0.22-2.fc13.x86_64 Ankur
(In reply to comment #6) > *** Bug 622092 has been marked as a duplicate of this bug. *** Thanks Jason!
right - obexd-0.22-2.fc13.x86_64. (and nothing to do with NetworkManager. I confused it with the bluetooth applet)
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Updating to F15. Haven't used obex-push for a while though. Bastien, could you please close the bug if it's been fixed? I'll try to reproduce it later tonight.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping