kernel-packages team mailing list archive

[Kristoffer <kristoffer.odmark90@xxxxxxxxx>]

I have the same problem

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/495696

Title:
  blueman fails to release rfcomm0 when "disconnect device" is used with
  SP or DUN profile connections

Status in Blueman - Bluetooth Manager:
  In Progress
Status in “bluez” package in Ubuntu:
  Invalid

Bug description:
  In the Blueman Device Manager, the bottom-most "Disconnect" context
  menu option doesn't work well (at least with SP and DUN profile
  connections).  It leaves the /dev/rfcommX port open (by bluetoothd).
  However, the profile-specific disconnect option at the top of the menu
  works properly.

  Blueman should keep track of open connections and properly close any
  associated ports.

  Steps to reproduce:

  1) set up a SPP or DUN connection.
  2) right click on the device in blueman device manager and click the bottom-most menu item, Disconnect device.
  3) try to reconnect as SPP or DUN.  Result: "Connection failed: port already in use"

  However, disconnecting the SPP or DUN connection using "Disconnect
  Serial port rfcomm0", etc works (releases rfcomm0 and a reconnect
  therefore works)

  This occurs on my laptop using a Dell Wireless 360 bluetooth module
  (internal USB), and also on my desktop using an external USB bluetooth
  module.

  Laptop lsusb line:
  Bus 006 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
  Desktop lsusb line:
  Bus 007 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

  I'm assuming it's not device specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/495696/+subscriptions