hcid crashed with SIGSEGV in g_main_context_dispatch()

[wizir]

Binary package hint: bluez-utils

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu intrepid (development branch)
Release: 8.10

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
bluez-utils:
  Zainstalowana: 3.36-1ubuntu1
  Kandydująca: 3.36-1ubuntu1
  Tabela wersji:
 *** 3.36-1ubuntu1 0
        500 http://pl.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Problem occured immediately after sudo apt-get update && sudo apt-get upgrade
----------------------

ProblemType: Crash
Architecture: i386
Disassembly: 0xf5be0000:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/hcid
Package: bluez-utils 3.36-1ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/hcid -x -s
ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: bluez-utils
Stacktrace:
 #0 0xf5be0000 in ?? ()
 #1 0xb7e667e1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 #2 0xb7e69e83 in ?? () from /usr/lib/libglib-2.0.so.0
 #3 0xb7e6a3a2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 #4 0xb7f30bf2 in main () from /usr/sbin/hcid
StacktraceTop:
 ?? ()
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 main () from /usr/sbin/hcid
Title: hcid crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.26-5-generic i686
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libglib-2.0.so.0
g_main_loop_run () from /usr/lib/libglib-2.0.so.0
main (argc=3, argv=0xf5be0000) at main.c:947

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!