Bluetooth stopped working / device adapter isn't found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bluez
A few days ago my bluetooth stopped working on my new Samsung r580, it was working at first and then suddenly the bluetooth applet dissappeared and the device adapter isn't found.
system info:
---------------
samsung r580 laptop
ubuntu 10.10
package info:
----------------
bluez:
Installed: 4.69-0ubuntu2
Candidate: 4.69-0ubuntu2
Version table:
*** 4.69-0ubuntu2 0
500 http://
100 /var/lib/
lspci:
-------
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series]
01:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01)
06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
bluetoothd -nd:
-------
bluetoothd[4714]: Bluetooth deamon 4.81
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: src/main.
bluetoothd[4714]: Unable to get on D-Bus
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bluez 4.69-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sun Dec 12 23:37:23 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterestingModules: rfcomm sco bnep l2cap bluetooth
MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 09/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 03KP.M008.
dmi.board.
dmi.board.name: R540/R580/
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 03KP
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: R540/R580/
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
hciconfig:
rfkill:
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.