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

[Richard King]

this bug occured as i was trying to connect my bluetooth headset to the system.
2 times this same error within 10 munites.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu16
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 21 17:26:56 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-03-17 (3 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130317)
MarkForUpload: True
ProcCmdline: gnome-control-center bluetooth
SegvAnalysis:
 Segfault happened at: 0x7f76da4c8d5b: mov 0x8(%rax),%rdi
 PC (0x7f76da4c8d5b) 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
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.11
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: [bluetooth]: gnome-control-center crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 25.5-0ubuntu1
 gnome-control-center-signon 0.1.3bzr13.02.20-0ubuntu1
 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1
 indicator-datetime 12.10.3daily13.03.07-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 bluetooth_chooser_get_selected_device_data (self=0x7f77166c2da0, column=column@entry=1) at bluetooth-chooser.c:231
 bluetooth_chooser_get_selected_device (self=<optimized out>) at bluetooth-chooser.c:250
 connect_done (source_object=0x7f7716a905c0, res=<optimized out>, user_data=0x7f7716c7af50) at cc-bluetooth-panel.c:174
 g_simple_async_result_complete (simple=0x7f7716bed090) at /build/buildd/glib2.0-2.35.8/./gio/gsimpleasyncresult.c:777
 complete_in_idle_cb (data=0x7f7716bed090) at /build/buildd/glib2.0-2.35.8/./gio/gsimpleasyncresult.c:789

[vinesh (vinesh-redhat-bugs)]

Version-Release number of selected component:
control-center-3.8.2-1.fc19

Additional info:
reporter: libreport-2.1.4
backtrace_rating: 4
cmdline: gnome-control-center sound
crash_function: bluetooth_chooser_get_selected_device_data
executable: /usr/bin/gnome-control-center
kernel: 3.9.2-301.fc19.x86_64
runlevel: N 5
uid: 1000
xsession_errors:

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 bluetooth_chooser_get_selected_device_data at bluetooth-chooser.c:231
 #1 bluetooth_chooser_get_selected_device at bluetooth-chooser.c:250
 #2 connect_done at cc-bluetooth-panel.c:176
 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #4 complete_in_idle_cb at gsimpleasyncresult.c:789
 #8 g_main_context_iteration at gmain.c:3762
 #9 g_application_run at gapplication.c:1623

Potential duplicate: bug 804857

[vinesh (vinesh-redhat-bugs)]

Created attachment 750817
File: backtrace

[vinesh (vinesh-redhat-bugs)]

Created attachment 750818
File: cgroup

[vinesh (vinesh-redhat-bugs)]

Created attachment 750819
File: core_backtrace

[vinesh (vinesh-redhat-bugs)]

Created attachment 750820
File: dso_list

[vinesh (vinesh-redhat-bugs)]

Created attachment 750821
File: environ

[vinesh (vinesh-redhat-bugs)]

Created attachment 750822
File: limits

[vinesh (vinesh-redhat-bugs)]

Created attachment 750823
File: maps

[vinesh (vinesh-redhat-bugs)]

Created attachment 750824
File: open_fds

[vinesh (vinesh-redhat-bugs)]

Created attachment 750825
File: proc_pid_status

[vinesh (vinesh-redhat-bugs)]

Created attachment 750826
File: var_log_messages

[Olivier (olivier-redhat-bugs)]

Trying to connect to a another Fedora 19 machine using bluetooth

reporter: libreport-2.1.6
backtrace_rating: 4
cmdline: gnome-control-center bluetooth
crash_function: bluetooth_chooser_get_selected_device_data
executable: /usr/bin/gnome-control-center
kernel: 3.9.9-302.fc19.x86_64
package: control-center-3.8.3-2.fc19
reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV)
runlevel: N 5
uid: 500

[Launchpad Janitor (janitor)]

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

[Fedora (fedora-redhat-bugs)]

This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[Fedora (fedora-redhat-bugs)]

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.