bluetooth-sendto crashed with SIGSEGV in device_changed()

Bug #855549 reported by Jeff Lane 
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
GNOME Bluetooth
Invalid
Critical
gnome-bluetooth (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Found while trying to send a file to my phone from this laptop as part of a test. This is on Oneiric after updating to the latest bits as of 21 Sept. I tried sending a file and then apport fired and told me that this had crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.1.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CheckboxSubmission: c15324ae4708eb5bd3d4cf1e20520481
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Wed Sep 21 09:15:49 2011
ExecutablePath: /usr/bin/bluetooth-sendto
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915.1)
ProcCmdline: bluetooth-sendto
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1672f38a0c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f1672f38a0c) ok
 source "(%rax)" (0x4058000000000000) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: bluetooth-sendto crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0xa7b280, iface_type=10980880) at /build/buildd/glib2.0-2.29.92/./gobject/gtype.c:3985
 device_changed (device=0x9a6c30, property=0xc24b90 "Connected", value=0xc3c090, user_data=0xa7b280) at bluetooth-client.c:384
 marshal_dbus_message_to_g_marshaller (closure=0xabe1f0, return_value=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=0x7fff882740a0, marshal_data=0x0) at dbus-gproxy.c:1733
 g_closure_invoke (closure=0xabe1f0, return_value=0x0, n_param_values=3, param_values=0xa4f190, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=1867, instance=0x9a6c30, emission_return=0x0, instance_and_params=0xa4f190) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3272

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
summary: - bluetooth-sendto crashed with SIGSEGV in g_type_check_instance_cast()
+ bluetooth-sendto crashed with SIGSEGV in device_changed()
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=661173

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Triaged
Changed in gnome-bluetooth:
importance: Undecided → Unknown
status: New → Unknown
Changed in gnome-bluetooth:
importance: Unknown → Critical
status: Unknown → New
Changed in gnome-bluetooth:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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