Package: bluez Version: 4.97-1 Severity: normal Dear Maintainers,
I'm getting this syslog error when starting bluetoothd, i.e. on startup: bluetoothd[5100]: Parsing /etc/bluetooth/proximity.conf failed: No such file or directory Yes, blueproximity is installed; anyway, $ dpkg -S proximity.conf dpkg-query: Kein Pfad gefunden, der auf Muster *proximity.conf* passt I was a bit confused, did I miss something? Seems that the issue was solved upstream: "[PATCH BlueZ] Fix error when proximity config file is missing" ¹ ¹ http://comments.gmane.org/gmane.linux.bluez.kernel/15221 But if you like users to keep configuration options in /etc/bluetooth/proximity.conf, would you please provide a template file? Best, Sebastian -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'testing'), (100, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.17-vs2.3.2.1-dq67sw+ (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.5.8-1 ii libc6 2.13-24 ii libcap-ng0 0.6.6-1 ii libdbus-1-3 1.5.8-1 ii libglib2.0-0 2.30.2-5 ii libreadline6 6.2-8 ii libudev0 175-3 ii libusb-0.1-4 2:0.1.12-20 ii lsb-base 3.2-28 ii module-init-tools 4.0.3-1 ii python-dbus 0.84.0-2 ii python-gobject 3.0.3-2 ii udev 175-3 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
