[Pkg-bluetooth-maintainers] Bug#549341: bluez: rfcomm exit code 0 on error
Marcin Szewczyk, Wodny
wodny1 at gmail.com
Fri Oct 2 16:12:12 UTC 2009
Package: bluez
Version: 4.42-2
Severity: wishlist
The rfcomm tool returns exit code 0 on many errors.
Example:
$ rfcomm connect 0 00:00:00:00:00 10; echo $?
Can't connect RFCOMM socket: Operation now in progress
0
It causes problems in scripts.
There was a thread on gmane:
http://thread.gmane.org/gmane.linux.bluez.kernel/1100/focus=1106
But the problem seams to still exist in version 4.54.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bluez depends on:
ii dbus 1.2.16-2 simple interprocess messaging syst
ii libbluetooth3 4.42-2 Library to use the BlueZ Linux Blu
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst
ii libglib2.0-0 2.20.5-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-13 userspace USB programming library
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
ii makedev 2.3.1-89 creates device files in /dev
ii module-init-tools 3.10-3 tools for managing Linux kernel mo
ii udev 0.141-2 /dev/ and hotplug management daemo
bluez recommends no packages.
Versions of packages bluez suggests:
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-gobject 2.18.0-1 Python bindings for the GObject li
-- no debconf information
More information about the Pkg-bluetooth-maintainers
mailing list