Package: bluez Version: 4.94-2 Severity: normal After configuring a bluetooth mouse for the first time, all is fine and the mouse is working.
But after turning the mouse off and on again, or after reboot, or after long idle time (mouse sleeping?), the bluetooth mouse cannot reconnect to the system again. It needs to be removed and configured again, so the coniguration is working for one session only. This is quite nasty, as the configuration (using the GUI, e.g. bluetooth- wizard) is possible only with a working mouse ... so another (USB-)mouse is required, which makes the bluetooth mouse quite useless. The system here is an old powerpc minimac; tried this with a logitech bluetooth mouse and an IBM/lenovo bluetooth mouse. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 2.6.39-2-powerpc Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.4.12-5 simple interprocess messaging syst ii libbluetooth3 4.94-2 Library to use the BlueZ Linux Blu ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libcap-ng0 0.6.6-1 An alternate POSIX capabilities li ii libdbus-1-3 1.4.12-5 simple interprocess messaging syst ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libudev0 172-1 libudev shared library ii libusb-0.1-4 2:0.1.12-17 userspace USB programming library ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii module-init-tools 3.16-1 tools for managing Linux kernel mo ii python-dbus 0.84.0-1 simple interprocess messaging syst ii python-gobject 2.28.6-4 Python bindings for the GObject li ii udev 172-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
