gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete() during bluetooth connection

Bug #1268527 reported by Piotr Plenik on 2014-01-13
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME

Bug Description

This problem always appear when I connect bluetooth a2dp device.
To duplicate problem:
1. Open Bluetooth settings;
2. Connect to device;
3. Before successful connect, go to sound configuration.

I have Creative D80, but i think this problem appear with other devices.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.10.1-0ubuntu1~saucy3 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 13 10:49:41 2014
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-03-12 (306 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
 Segfault happened at: 0x7f2c33eb8843: mov 0x8(%rax),%rdi
 PC (0x7f2c33eb8843) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
 ?? () from /usr/lib/
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/
Title: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to saucy on 2013-10-22 (82 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
 gnome-control-center-unity 1.3+13.10.20131004-0ubuntu1

Piotr Plenik (piotr-plenik-f) wrote :
Ubuntu GNOME (ug-bot) wrote :

 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace

Barneedhar, I found in activity log, that you mark this issue as duplicated.
Could you specify, with issue describe this problem?

information type: Private → Public
information type: Public → Public Security
description: updated
Changed in ubuntu-gnome:
assignee: nobody → Wilder Ruiz Castillo (poisoncadc)
assignee: Wilder Ruiz Castillo (poisoncadc) → nobody

This bug many times cut off the start of the system Ubuntu GNOME ,
Title : gnome - shell crashed with SIGSEGV in g_simple_async_result_complete()
Apport version:2.13.3-0ubuntu1
Architecture: amd64
Current Desktop : GNOME
Disassembly=> 0x 7fff000000c7: No se puede acceder a la memoria en la direccion 0x 7fff000000c7

Sometimes after notify the error , the system report a problem in gnome-shell
"el problema no puede notificarse :

Tiene algunos paquetes instalados con versiones obsoletas . Actualice los siguientes paquetes y compruebe si el problema persiste :

gstreamer1.0-plugins-good, iputils-arping, libbgtreamer-plugins-good1.0-0,libreadline6,python-apt-common, python-cuphelpers, python3-apt, readline-common, system-config-printer-common, system-config-printer-gnome, system-config-printer-udev, usb-modeswitch-data"

With all the respect and attentively ,today march 20 of 2014 ask for help and waiting for early response , WIlder Ruiz

Changed in ubuntu-gnome:
status: New → Invalid
fermulator (fermulator) wrote :

This is easily reproducible.

Exactly as the reporter has indicated. Happens to me on a daily basis if I too quickly go from Bluetooth to Sound configuration.

e.g. typical activity is:
1. turn on system (Ubuntu 14.04 for me)
2. open Bluetooth settings, and initiate a connection to the bluetooth speaker
 (there's a /different/ bug probably, in that when we change audio output, the SOUND volume does not automatically switch)
3. so go back, then into Sound settings to select the Bluetooth speaker connection.

Sometimes, between #2 and #3, the bluetooth connection may not always work, OR, it takes a bit longer and if we try to go back BEFORE the connection is initiated, the gnome control center will crash.

Changed in ubuntu-gnome:
status: Invalid → Confirmed
summary: gnome-control-center crashed with SIGSEGV in
- g_simple_async_result_complete()
+ g_simple_async_result_complete() during bluetooth connection
Bruce Pieterse (octoquad) wrote :

Bug report is sufficient.

To post a comment you must log in.
This report contains Public Security information  Edit
Everyone can see this security related information.

Duplicates of this bug

Other bug subscribers