touch-packages team mailing list archive

[Huck-bernhard <huck.bernhard@xxxxxxxxxx>]

addition:

if you call bluez-test-discovery few  times stops discoverry of devices  complete.
I can see a similar behavior at StartDiscovery  with DBUS "org.bluez.Adapter" with QT5 and QDBusInterface
after connecting a device and disconnect because of distance device to long is Discovery also stopt. 
after calling: "hciconfig reset"  is Discovery working again.
this error is only at Ubuntu 14.10. with 14.04 is it working

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
      Trusted = 0
      Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in maybe_handle_message
      self._handler(*args, **kwargs)
    File "/usr/bin/bluez-test-discovery", line 15, in device_found
      value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:	Type: BR/EDR  Bus: USB
   	BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
   	UP RUNNING PSCAN 
   	RX bytes:1318 acl:0 sco:0 events:55 errors:0
   	TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
   	Soft blocked: no
   	Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1392829/+subscriptions