[Pkg-bluetooth-maintainers] Bug#836982: bluez: File transfers to computer end up in wrong directory ~/.cache/obexd

[Torquil Macdonald Sørensen]

Package: bluez
Version: 5.40-1~exp0+b1
Severity: normal

File transfers to my computer should end up in ~/Bluetooth_shared according to my
settings in blueman-applet, but they end up in ~/.cache/obexd instead.

If I keep "btmon" running during a file transfer, I see this error message:

= bluetoothd: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)

Best regards,
Torquil Sørensen

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bluez depends on:
ii  dbus                 1.10.10-1
ii  init-system-helpers  1.42
ii  kmod                 22-1.1
ii  libc6                2.24-2
ii  libdbus-1-3          1.10.10-1
ii  libglib2.0-0         2.49.6-1
ii  libreadline6         6.3-8+b4
ii  libudev1             231-5
ii  lsb-base             9.20160629
ii  udev                 231-5

bluez recommends no packages.

bluez suggests no packages.

-- no debconf information