Package: obexd-client Version: 0.48-1 Followup-For: Bug #718596 I am suspecting that the issue is similar to what was reported here https://bugs.archlinux.org/task/31122 and forwarded https://bugzilla.gnome.org/show_bug.cgi?id=682106 which points out that the new obexd has a completely different API.
Presumably the version of bluez in unstable is incompatible with this new API. There is bluez 5.5-1~exp1 in experimental, though simply installing it straight up fails with "Starting bluetooth: bluetoothd rfcomm/usr/bin/rfcomm: invalid option -- 'f'" instead... -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages obexd-client depends on: ii libbluetooth3 4.101-2 ii libc6 2.17-92 ii libdbus-1-3 1.6.12-1 ii libglib2.0-0 2.36.3-4 obexd-client recommends no packages. obexd-client suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
