Your message dated Thu, 29 Oct 2009 18:28:05 +0100
with message-id <20091029182805.65c93...@bluepaper>
and subject line Fixed in bluez 4.56-1
has caused the Debian Bug report #547552,
regarding bluez: bluetoothd segfault on usb dongle insertion
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
547552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547552
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bluez
Version: 4.42-2
Severity: grave
Justification: renders package unusable
When I insert a USB Bluetooth Dongle, I've recently started seeing the
following output in dmesg:
[31108.769042] usb 5-1: new full speed USB device using uhci_hcd and
address 6
[31108.927155] usb 5-1: New USB device found, idVendor=0a12,
idProduct=0001
[31108.927159] usb 5-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[31108.927287] usb 5-1: configuration #1 chosen from 1 choice
[31108.930294] bluetoothd[17867]: segfault at 7fb82caee4 ip
00007fb82c8117cf sp 00007fff22aa3b30 error 4 in
libc-2.9.so[7fb82c7a0000+147000]
This failure renders bluetooth completely unusable on my system -
neither kbluetooth and gnome's bluetooth-applet can enable bluetooth,
and hcitool scan reports:
Device is not available: No such device
Wammu is also unable to detect or connect to my mobile phone, which I
was able to do using this dongle about a week ago - so I don't think
this is a hardware incompatibility problem.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (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
--- End Message ---
--- Begin Message ---
fixed 547552 4.56-1
thanks
Hi,
this issue is no more reproducible. I've tested it with latest bluez
package and everything seems to work the right way here.
Therefore I'm closing this bug, feel free to re-open if you find this
issue again.
Andrea
--- End Message ---
