segfault in bluetoothd

Bug #393172 reported by Florian Hars
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bluez

I tried to use a bluetooth dongle to transfer some files from my phone (which worked on another computer and gutsy or hardy, don't remember which), and one result I got was:

[ 5014.824039] usb 5-1: new full speed USB device using uhci_hcd and address 2
[ 5015.264163] usb 5-1: configuration #1 chosen from 1 choice
[ 5015.325106] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 5015.325601] usbcore: registered new interface driver btusb
[ 5268.841743] bluetoothd[2620]: segfault at 656c6966 ip 656c6966 sp bfb29cbc error 4 in gconv-modules.cache[b7be3000+7000]

I have not found a way to reproduce this, but bluetooth still doesn't work, I can (partially) browse the files on the phone, but have not managed to transfer even one file, most of the time the file manager just closes without any error message whatsoever when opening a folder, sometimes it says "not connected" when trying to open a file.

One error I got which may be related (but which is not reproducible) was:
[ 5914.757115] AppArmor Debug: Hook being called from interrupt context
[ 5914.757122] Pid: 3253, comm: compiz.real Tainted: P 2.6.28-13-generic #44-Ubuntu
[ 5914.757125] Call Trace:
[ 5914.757133] [<c04fca36>] ? printk+0x18/0x1a
[ 5914.757138] [<c02a6377>] aa_revalidate_sk+0x97/0xa0
[ 5914.757141] [<c02a84b0>] apparmor_socket_sendmsg+0x10/0x20
[ 5914.757144] [<c0287c20>] security_socket_sendmsg+0x10/0x20
[ 5914.757149] [<c0422d57>] sock_sendmsg+0xc7/0x110
[ 5914.757154] [<c014ecb0>] ? autoremove_wake_function+0x0/0x50
[ 5914.757157] [<c01ae5af>] ? dma_pool_alloc+0x10f/0x120
[ 5914.757161] [<c03d414a>] ? uhci_submit_common+0x1aa/0x2c0
[ 5914.757164] [<c0423000>] kernel_sendmsg+0x30/0x50
[ 5914.757167] [<c04d964b>] rfcomm_send_disc+0x8b/0xa0
[ 5914.757170] [<c04da978>] __rfcomm_dlc_close+0x188/0x1c0
[ 5914.757172] [<c04daa90>] rfcomm_encrypt_cfm+0xe0/0xf0
[ 5914.757175] [<c04da9b0>] ? rfcomm_encrypt_cfm+0x0/0xf0
[ 5914.757178] [<c04d0ed9>] hci_encrypt_cfm+0x79/0xa0
[ 5914.757180] [<c04d2cee>] hci_event_packet+0xe8e/0x1220
[ 5914.757184] [<c03b8a41>] ? usb_free_urb+0x11/0x20
[ 5914.757186] [<c03b71f9>] ? usb_hcd_giveback_urb+0x59/0xc0
[ 5914.757189] [<c04fec68>] ? _spin_lock+0x8/0x10
[ 5914.757192] [<c03d2d2e>] ? uhci_giveback_urb+0x8e/0x1f0
[ 5914.757195] [<c03d290b>] ? uhci_result_common+0xbb/0x2f0
[ 5914.757197] [<c04d3c49>] ? hci_send_to_sock+0x19/0x160
[ 5914.757200] [<c04ce979>] hci_rx_task+0x209/0x270
[ 5914.757203] [<c03d3596>] ? uhci_scan_schedule+0x196/0x260
[ 5914.757206] [<c013ed18>] tasklet_action+0x78/0x100
[ 5914.757209] [<c013f197>] __do_softirq+0x97/0x170
[ 5914.757212] [<c011c7df>] ? ack_apic_level+0x6f/0x290
[ 5914.757215] [<c013f2cd>] do_softirq+0x5d/0x60
[ 5914.757218] [<c013f445>] irq_exit+0x55/0x90
[ 5914.757221] [<c0106853>] do_IRQ+0x83/0xa0
[ 5914.757225] [<c01bddfd>] ? sys_read+0x3d/0x70
[ 5914.757227] [<c01051f3>] common_interrupt+0x23/0x30

----------------------- System information:

Description: Ubuntu 9.04
Release: 9.04

bluez:
  Installed: 4.32-0ubuntu4.1
  Candidate: 4.32-0ubuntu4.1
  Version table:
 *** 4.32-0ubuntu4.1 0
        500 http://ftp.hosteurope.de jaunty-updates/main Packages
        100 /var/lib/dpkg/status
     4.32-0ubuntu4 0
        500 http://ftp.hosteurope.de jaunty/main Packages

Bus 005 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
Suco (sucotronic) wrote :

Just after installing bluetooth dongle:
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

When I try to explore my phone through bluetooth nautilus suddenly closes and in the log it says:

kernel: [ 766.094836] nautilus[6197]: segfault at 0 ip b78ff3d7 sp bfd37014 error 4 in libglib-2.0.so.0.2000.1[b78a2000+b6000]

Very annoying to have latest ubuntu version and not being able to explore a normal mobile phone.

Revision history for this message
Mörgæs (moergaes) wrote :

Closing due to age.
If a similar bug appears in 13.10 please open a new report.

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

Other bug subscribers

Remote bug watches

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