[bluetooth]: gnome-control-center crashed with SIGSEGV in device_changed()

Bug #1057398 reported by criser on 2012-09-27
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Medium
Unassigned

Bug Description

Crashed when sending file to the device. File is successfully sent.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu15
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 27 11:07:04 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f72782dbdbc <g_type_instance_get_private+188>: mov (%rbx),%rax
 PC (0x7f72782dbdbc) ok
 source "(%rbx)" (0x4058000000000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_instance_get_private () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libgnome-bluetooth.so.11
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_instance_get_private()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.92-0ubuntu1
 gnome-control-center-signon 0.0.17-0ubuntu1
 indicator-datetime 12.10.1-0ubuntu1

criser (criser1234) wrote :

StacktraceTop:
 g_type_instance_get_private (instance=instance@entry=0x7f727bf17000, private_type=140129683325904) at /build/buildd/glib2.0-2.33.14/./gobject/gtype.c:4517
 device_changed (client=0x7f727bf17000, variant=0x7f727c14f4c0, property=0x7f727c18d270 "Connected", device=0x7f727c0da4e0) at bluetooth-client.c:433
 device_g_signal (client=0x7f727bf17000, parameters=<optimized out>, proxy=0x7f727c0da4e0, sender_name=<optimized out>, signal_name=<optimized out>) at bluetooth-client.c:500
 device_g_signal (proxy=0x7f727c0da4e0, sender_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, client=0x7f727bf17000) at bluetooth-client.c:487
 ffi_call_unix64 () at ../src/x86/unix64.S:75

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, is that still an issue in the current version? It could have been fixed by https://bugzilla.gnome.org/show_bug.cgi?id=681456

information type: Private → Public
summary: - gnome-control-center crashed with SIGSEGV in
- g_type_instance_get_private()
+ [bluetooth]: gnome-control-center crashed with SIGSEGV in
+ device_changed()
Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
affects: gnome-control-center (Ubuntu) → gnome-bluetooth (Ubuntu)
Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-bluetooth - 3.8.2.1-0ubuntu4

---------------
gnome-bluetooth (3.8.2.1-0ubuntu4) trusty; urgency=medium

  * debian/patches/git_disconnect_callbacks.patch,
    debian/patches/git_leak_fixes.patch,
    debian/patches/git_reference_handling.patch:
    - backport some fixes, should resolve some segfaults issues (lp: #1057398)
 -- Sebastien Bacher <email address hidden> Tue, 25 Feb 2014 16:32:43 +0100

Changed in gnome-bluetooth (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
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.