cannot get files from bluetooth device - copying hangs forever, makes nautilus eat 100%CPU

Bug #696258 reported by Teo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: nautilus

There must be more than one bug here, both in the package implementing bluetooth funcionalities, and in Nautilus itself - anyway it is hard for me to distinguish so the only thing I can do is report the problem as a whole.

When trying to copy files from my phone to my computer via bluetooth I get the following problem

1) On my phone, I turn bluetooth on, I turn on its bluetooth visibility and make my files visible
2) In Ubuntu, I click on the bluetooth icon on the panel and select "browse files on device..."
3) I select the device and click "browse"
4) On the phone, I am prompted to allow the Pc to access the files; I accept
5) On the computer, a Nautilus window opens which allows me to browse the folders and files on the phone
6) In Nautilus, I leave this window open and I open a new one to browse my local hard disk
7) In Nautilus, I select the files on my phone and drag'n'drop them into a folder in my computer
8) Now on the phone I am prompted to give the Pc permission to get the files, and here the problems begin

Normally, my phone would prompt me for each file to allow the transfer, and I would always accept.
At random times, the following happens:

9) At any point, after accepting on the phone to allow getting the n-th file, the computer gets stuck and never goes on; the phone never prompts me to accept to allow getting the (n+1)-th file.

This is the first bug (computer is failing to send the request for the following files; or the request has been lost for any reason, in which case the computer should either resend it or pop up an error message reporting the problem to the user, not just hang on forever)

10) Nautilus every once in a while starts consuming 100% CPU for a few seconds and then goes back to normal

11) the "File Operations" windows stays open and shows a "copying <N> files to <folder name>" progress bar which is stuck at a certain percentage and never goes on. If I click on the "X" on the right to abort the operation, the "X" turns gray but the operation is never aborted and the "File Operation" window stays open forever

Here's the second clear bug in Nautilus: the file operation is not aborted.

12) If I close the "file operation" windows the way yoy close any window (with the close icon on the window's title bar), the window closes, but the icon on the panel indicating a copy operation still remains. By clicking on that icon on the panel, there is a "show copy dialog" option: if I click it, the copy dialog shows up again (and the progress bar is still at the same point).

So basically there's no way to abort that copy operation other than manually killing the process or restarting the computer.

13) Nautilius still eats 100% CPU at random times.

So I think there are a couple of separate but related issues:

A) Bluetooth protocol implementation is terribly buggy. Copying files from a device can hang at any point. It is even possible that the phone's software is buggy and that the phone is not behaving correctly, but even if this is the case, the computer's response is unacceptable: it should give an error message and stop the operation, not hang on forever

B) Nautilus has an issue in that when you try to abort a copy operation by clicking on the "X" on the right next to the progress bar, the abortion fails and the copy operation gets stuck forever and Nautilus even eats 100%CPU.

** After restarting the computer and repeating the process again and again, I get almost always the same result (with point 9 happening at any time, i.e. sometimes after the first file sometimes after copying N files, with varying N). Sometimes, instead, I get a different, still nonsense, behaviour:

after point (8), and after I allow the transfer from the phone, I get a nonsense error message of which I remember the words "error" and "another operation" - something like "error copying file xxxxx: another operation is pedning" (these are not the exact words).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Jan 1 15:34:22 2011
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

Revision history for this message
Teo (teo1978) wrote :
Revision history for this message
Omer Akram (om26er) wrote :

could you try Ubuntu-10.10 to see if that version solves the problem for you? you could download the ISO and start it in Live session just to check if the issue is present there too.

Changed in nautilus (Ubuntu):
status: New → Incomplete
Omer Akram (om26er)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Teo (teo1978) wrote :

Well I cannot test it on 10.10 but I don't think that's a reason for closing the bug

Changed in nautilus (Ubuntu):
status: Expired → New
Changed in nautilus (Ubuntu):
importance: Medium → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no such issue reported in years, and it seems to work fine, assuming it doesn't exist in the current version of the code and closing

Changed in nautilus (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.