bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

Bug #857702 reported by LostinSpacetime on 2011-09-23
This bug affects 57 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)

Bug Description

I don't know if this is a duplicate ob bug #280878. I didn't have it with 11.04 but only with 11.10.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 23 15:24:53 2011
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Hewlett-Packard HP Compaq 6735b
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=f2cf15d8-c520-4753-82b5-bad3fe675087 ro quiet splash vt.handoff=7
 Segfault happened at: 0x697812: movl $0x0,0x240(%eax)
 PC (0x00697812) ok
 source "$0x0" ok
 destination "0x240(%eax)" (0x00000240) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: bluez
 ?? ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/
 g_main_context_dispatch () from /lib/i386-linux-gnu/
 ?? () from /lib/i386-linux-gnu/
Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GTT Ver. F.13
dmi.board.asset.tag: Base Board Asset Tag 30E3
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.24
dmi.chassis.asset.tag: CNU91556Y3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68GTTVer.F.13:bd12/08/2009:svnHewlett-Packard:pnHPCompaq6735b:pvrF.13:rvnHewlett-Packard:rn30E3:rvrKBCVersion96.24:cvnHewlett-Packard:ct10:cvr: HP Compaq 6735b
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:24:7E:4D:86:F9 ACL MTU: 1017:8 SCO MTU: 64:8
  RX bytes:1027 acl:0 sco:0 events:29 errors:0
  TX bytes:628 acl:0 sco:0 commands:29 errors:0

 device_event (event=<optimized out>, index=0) at plugins/hciops.c:2654
 io_stack_event (chan=0x217d4608, cond=G_IO_IN, data=0x0) at plugins/hciops.c:2763
 g_io_unix_dispatch (source=0x217d4650, callback=0x697d00 <io_stack_event>, user_data=0x0) at /build/buildd/glib2.0-2.29.92/./glib/giounix.c:166
 g_main_dispatch (context=0x217d24a0) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:2441
 g_main_context_dispatch (context=0x217d24a0) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:3011

Changed in bluez (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: New → Confirmed
visibility: private → public
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing

Also present in 12.04 beta.

Not sure how to re-produce as it appears to happen shortly after logging in.

tsj (ts3141592) wrote :

Same as Johan Heinrichs: running beta1 12.04 and shortly after login receive message "Bluetoothd has closed unexpectedly."

In addition, trying to turn off bluetooth through the applet kills the wireless instead for which I intend to file a separate bug.

Diego Schulz (dschulzg) wrote :

Same here, bluetooth crashed right after login.

(Running an updated 12.04 installation (~ Tue Mar 27 21:30:00 UTC 2012))

Chris J Arges (arges) wrote :

Crashed right after login.

Liam (liam-smit) wrote :

Also encountered on a Dell Latitude E5510 running 12.04 64 bit shortly after login.

uname -a
Linux liamlaptop 3.2.0-20-generic #33-Ubuntu SMP Tue Mar 27 16:42:26 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Yves-Antoine (yae) wrote :

Also crashed right after login on precise, after updating Beta 2 on Saturday 31 of March 2012.
Did not crash on Precise Beta1 (any update) or vanilla Beta2.

uname -a
Linux t520 3.2.0-21-generic #34-Ubuntu SMP Fri Mar 30 04:25:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

bluez 4.98-2ubuntu7

Sam_ (and-sam) on 2012-03-31
tags: added: precise
tags: added: amd64
Baldrick (bheath-nz) wrote :

Same here, though I'm using 12.04 beta2 and i386.

I was opening gwibber at the time.

anthropornis (anthropornis) wrote :

This affects me on a Lenovo Thinkpad T420i running Ubuntu 12.04 amd64 using Unity 3d.

This error occurs shortly after login, and did not start occurring until about 3 or 4 weeks ago. Before that I was running 12.04 without incident. Things seemed to changed after a round of updates (which I think included a kernel update, but subsequently choosing the previous kernel from the Grub menu has not helped either this, or the next problem ...).

This problem also did not seem to start occurring until another -- possibly related -- problem started occurring, after the same updates cycle. Periodically, after suspending my laptop, then taking it to my workplace where I was only using Wi-Fi -- without incident -- and then resuming my laptop, after a few hours the networking dies. The Wi-Fi icon still looks normal (and Wi-Fi networks are still listed), but the Dropbox icons in my panel go offline and I cannot connect to the Internet using web browsers, Thunderbird or the like. At the same time as this is happening, attaching an Ethernet cable will not work; the networking icon in the panel does not change to a "wired" icon, it remains as a wireless icon.

I ultimately have to reboot to get Ethernet to work (and rebooting only restores Wi-Fi for another few hours, so I avoid using Wi-Fi), and now I take a patch cable with me everywhere. And it is after this reboot that I receive the bluetoothd error dialog.

On the other hand, after leaving my workplace and attaching my Ethernet cable at home (after suspending the laptop once again), I don't have any error, unless I tried to "disable wireless" via the networking indicator at work. So it seems I have to leave Wi-Fi enabled or I get more crashes.

It seems like my new networking problem is related to this bluetoothd crash, or maybe I am mistaken, I don't know enough to tell.

anthropornis (anthropornis) wrote :

Think I am going to try uninstalling the bluez package altogether to see if all the errors will stop.

MrMur (murrayie) wrote :

99% Sure it didn't happen straight away with 12.04 but appeared after updates. Seems to happen after login and also if networking is disabled/re-enabled via kill-switch.

Rodrigo Primo (rodrigosprimo) wrote :

Any workaround for this? It is very annoying to see the error message several times per day.

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers