GNOME Bugzilla – Bug 741428
Can't copy files from a bluetooth device: Another operation in progress
Last modified: 2015-05-30 13:22:02 UTC
Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1284308 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy gvfs gvfs: Installed: 1.20.1-1ubuntu1 Candidate: 1.20.1-1ubuntu1 Version table: *** 1.20.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one pairs their bluetooth phone, browses it, and attempt to copy a file from the phone to Ubuntu, it does so successfully. 4) What happens instead is a window pops up noting: Error while copying “example.txt”. There was an error copying the file into /home/test/ Show more details Another operation in progress Originally reproduced in 13.10. /usr/lib/gvfs/gvfsd-obexftp 'host=[XX:XX:XX:XX:XX:XX]' ** Message: transfer of example.txt to /tmp/gvfsobexftp-tmp-NTNMQX started ** Message: filename: /Internal storage/Download/example.txt (example.txt) copying to /tmp/gvfsobexftp-tmp-NTNMQX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: ChangeCurrentFolderToRoot failed
Considering that there are, as of today, 55 persons reporting having the problem downstream, I believe that this bug can be marked as "Confirmed". This bug is serious and constant. Bluetooth is broken because of it. In my case, I never get a copy operation to work.
(In reply to comment #1) > Considering that there are, as of today, 55 persons reporting having the > problem downstream, I believe that this bug can be marked as "Confirmed". 1) We wouldn't know that if nobody mentions that on this bug 2) We don't make any difference between the UNCONFIRMED and NEW statuses. > This bug is serious and constant. Bluetooth is broken because of it. In my > case, I never get a copy operation to work. http://www.hadess.net/2011/11/obexftp-in-gnome-non-update.html
The funny thing about this bug is it only affects GNOME software. For example, suppose you are trying to copy pictures off your phone. Nautlius will fail to do it directly. You can open the pictures in EoG and view them, but if you try to save a copy of the picture locally you get the same error, even though the picture is displayed on screen and therefor must be readable. If you do the exact same thing with Firefox it works.
Obexftp backend has been obsoleted in GNOME 3.10, because it is incompatible with Bluez 5, however limited bluetooth support is currently built-in in GNOME desktop.
Ondrej Holy, I don't think closing a bug, when the functionality is still not in place, because the original technology isn't compatible as you advised, is doing the right thing by users here. Unless I may copy files off my phone via bluetooth, in whatever mechanism is or becomes supported via GNOME, this bug report is not considered closed.
(In reply to Christopher M. Penalver from comment #5) > Ondrej Holy, I don't think closing a bug, when the functionality is still > not in place, because the original technology isn't compatible as you > advised, is doing the right thing by users here. > > Unless I may copy files off my phone via bluetooth, in whatever mechanism is > or becomes supported via GNOME, this bug report is not considered closed. It can be closed because the code doesn't exist anymore. Take a look at bug 740882 for progress on reimplementing bluetooth support.
Ross Lagerwall, thank you for the quick response. >"It can be closed because the code doesn't exist anymore." Then it appears you don't understand the scope of this bug report. The scope of this report is the functionality only, not whichever backend may or may not support it, or how supportability applies to that backend. Hence, please stop toggling this report closed on some irrelevant technicality until the functionality is implemented. If you would like to contribute to this report, please re-assign it to the correct backend/package as applicable.
(In reply to Christopher M. Penalver from comment #7) > Ross Lagerwall, thank you for the quick response. > > >"It can be closed because the code doesn't exist anymore." > > Then it appears you don't understand the scope of this bug report. The scope > of this report is the functionality only, not whichever backend may or may > not support it, or how supportability applies to that backend. > > Hence, please stop toggling this report closed on some irrelevant > technicality until the functionality is implemented. > If a bluetooth backend is reimplemented, then it will support copying files from a bluetooth device, since this the most obvious feature to have. This would be done as part of bug 740882, so we don't need another bug open for it. Thanks
*** This bug has been marked as a duplicate of bug 740882 ***