[hardy] bluetooth-properties crashed with signal 5

Bug #188443 reported by Pjotr12345
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)

Bug Description

Binary package hint: bluez-gnome

It crashed when I tried to connect a TomTom One navigation device.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Feb 2 20:53:36 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/bluetooth-properties
NonfreeKernelModules: cdrom
Package: bluez-gnome 0.15-0ubuntu2
PackageArchitecture: i386
ProcCmdline: bluetooth-properties --singleton
ProcCwd: /home/ubuntu
Signal: 5
SourcePackage: bluez-gnome
 #0 0xb7e56fcc in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb7e57249 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0xb78c7fd4 in ?? () from /usr/lib/libdbus-glib-1.so.2
 #3 0x00000000 in ?? ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? ()
Title: bluetooth-properties crashed with signal 5
Uname: Linux ubuntu 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:dbus_g_proxy_begin_call_internal (proxy=0x8388ae0, method=<value optimized out>, notify=0,
dbus_g_proxy_call (proxy=0x8388ae0, method=0x8058cf3 "GetAdapter", error=0x0,
proxy_callback (proxy=0x8096ee0, call=0x2, user_data=0x8093a28) at input.c:76
d_pending_call_notify (dcall=0x8385c50, data=0x838a4b0) at dbus-gproxy.c:1728
_dbus_pending_call_complete (pending=0x8385c50) at dbus-pending-call.c:198

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in bluez-gnome:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers