← Back to team overview

kernel-packages team mailing list archive

[Bug 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device


Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu)
       Status: New => Confirmed

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files
  - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
   hci0:	Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to: