Package: bluez-utils Version: 2.18-1 Severity: wishlist Hello
When the 'rfcomm' kernel module isn't compiled with CONFIG_BT_RFCOMM_TTY enabled, 'rfcomm bind' will fail with an obscure error message, "Can't create device: Operation not supported". It does this when it's trying to bind to a device in /dev. Could this be changed to report something more useful, such as "Check rfcomm.ko is compiled with TTY support"? Peter. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-ck5 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages bluez-utils depends on: ii bluez-pin 0.25-1 Bluetooth PIN helper with D-BUS su ii dbus-1 0.23.4-3 simple interprocess messaging syst ii libbluetooth1 2.18-1 Library to use the BlueZ Linux Blu ii libc6 2.3.5-3 GNU C Library: Shared libraries an ii libusb-0.1-4 2:0.1.10a-18 userspace USB programming library ii module-init-tools 3.2-pre8-1 tools for managing Linux kernel mo ii modutils 2.4.27.0-3 Linux module utilities ii sysvinit 2.86.ds1-1 System-V like init bluez-utils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
