Package: bluez Version: 4.70-1 Severity: wishlist File: /usr/share/doc/bluez/README.Debian.gz
>From the README.Debian.gz, I used these commands to connect my new bluetooth keyboard: hcitool scan sudo bluez-simple-agent hci0 E8:06:88:52:C7:74 sudo bluez-test-input connect E8:06:88:52:C7:74 But I had to re-run the last command every time I rebooted or suspend-and-resumed! On a gentoo page[1] I learnt that I could run sudo bluez-test-device trusted E8:06:88:52:C7:74 yet ...and thereafter, I wouldn't have to re-run the "connect" line. It would be good if the README.Debian.gz mentioned this. [1] http://en.gentoo-wiki.com/wiki/Bluetooth_mouse -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.2.24-3 simple interprocess messaging syst ii libbluetooth3 4.70-1 Library to use the BlueZ Linux Blu ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libcap-ng0 0.6.4-1 An alternate posix capabilities li ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libglib2.0-0 2.25.13-1 The GLib library of C routines ii libnl1 1.1-5 library for dealing with netlink s ii libusb-0.1-4 2:0.1.12-16 userspace USB programming library ii lsb-base 3.2-25 Linux Standard Base 3.2 init scrip ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii python-dbus 0.83.1-1 simple interprocess messaging syst ii python-gobject 2.21.4+is.2.21.3-1 Python bindings for the GObject li ii udev 161-1 /dev/ and hotplug management daemo bluez recommends no packages. bluez 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