bluetooth-applet crashed with SIGSEGV in g_type_instance_get_private()

Bug #444814 reported by manuel
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

bluetooth

ProblemType: Crash
Architecture: i386
Date: Tue Oct 6 21:05:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/bluetooth-applet
NonfreeKernelModules: fglrx
Package: gnome-bluetooth 2.28.1-0ubuntu1
ProcCmdline: bluetooth-applet
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
SegvAnalysis:
 Segfault happened at: 0x41c7fd <g_type_instance_get_private+269>: mov (%esi),%eax
 PC (0x0041c7fd) ok
 source "(%esi)" (0x0000000a) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 g_type_instance_get_private ()
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV in g_type_instance_get_private()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
manuel (manuel-polce91) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_type_instance_get_private ()
add_killswitch (killswitch=0x9ba6fa0,
event_cb (source=0x9bb45d0,
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Making this a duplicate of the newer bug 445422, since it has more comments.

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.