bluetooth-applet crashed with SIGSEGV in strcmp()

Bug #322585 reported by stg
4
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: bluez-gnome

Bluetooth Applet crashes all the time after the second time I suspend the computer. I submitted the crash report through apport.

~$ lsb_release -a
LSB Version: core-2.0-ia32:core-3.0-ia32:core-3.1-ia32:core-3.2-ia32:core-2.0-noarch:core-3.0-noarch:core-3.1-noarch:core-3.2-noarch:cxx-2.0-ia32:cxx-3.0-ia32:cxx-3.1-ia32:cxx-3.2-ia32:cxx-2.0-noarch:cxx-3.0-noarch:cxx-3.1-noarch:cxx-3.2-noarch:desktop-3.1-ia32:desktop-3.2-ia32:desktop-3.1-noarch:desktop-3.2-noarch:graphics-2.0-ia32:graphics-3.0-ia32:graphics-3.1-ia32:graphics-3.2-ia32:graphics-2.0-noarch:graphics-3.0-noarch:graphics-3.1-noarch:graphics-3.2-noarch:languages-3.2-ia32:languages-3.2-noarch:multimedia-3.2-ia32:multimedia-3.2-noarch:printing-3.2-ia32:printing-3.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 8.04.2
Release: 8.04
Codename: hardy

If you need more information don't hesitate to ask I'll try my best to provide the required information.

Thanks

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/bluetooth-applet
NonfreeKernelModules: fglrx
Package: bluez-gnome 0.25-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: bluetooth-applet --singleton
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: bluez-gnome
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 g_str_equal () from /usr/lib/libglib-2.0.so.0
 ?? ()
 g_cclosure_marshal_VOID__STRING ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: bluetooth-applet crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.24-23-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner users video

Tags: apport-crash
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.