bluetoothd crashed with SIGSEGV in calloc()

[PaulJ01]

Binary package hint: bluez

Description: Ubuntu 8.10
Release: 8.10

bluez:
  Geïnstalleerd: 4.12-0ubuntu2
  Kandidaat: 4.12-0ubuntu2
  Versietabel:
 *** 4.12-0ubuntu2 0
        500 http://nl.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Bluez should start on startup or inserting the bluetooth dongle, showing a bluetooth icon in the panel.
Instead a crash is reported, as described in the summary.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/bluetoothd
NonfreeKernelModules: nvidia
Package: bluez 4.12-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: bluez
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 calloc () from /lib/tls/i686/cmov/libc.so.6
 dbus_malloc0 () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: bluetoothd crashed with SIGSEGV in calloc()
Uname: Linux 2.6.27-7-generic i686
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:_int_malloc () from /lib/tls/i686/cmov/libc.so.6
calloc () from /lib/tls/i686/cmov/libc.so.6
dbus_malloc0 (bytes=40) at dbus-memory.c:524
_dbus_timeout_new (interval=25000, handler=0xb7f77fc0 <reply_handler_timeout>,
_dbus_pending_call_new_unlocked (connection=0xb969f708,

[Oded Arbel (oded-geek)]

I just had a apport report a crash, which I think is the same as this bug. I believe this crash is the result of the laptop coming back from sleep and I previously reported a bug about bluetooth not working when coming back from sleep in bug #402930. I believe its also the same problem.

BTW - I'm using Karmic.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.