kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #179130
[Bug 776363] Re: Bluetooth service needs to be restarted before a Bluetooth dongle works
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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/776363
Title:
Bluetooth service needs to be restarted before a Bluetooth dongle
works
Status in bluez package in Ubuntu:
Invalid
Bug description:
Binary package hint: bluez
I can't turn bluetooth on with a dongle plugged in, unless I issue the command "sudo service bluetooth restart". This occurs when the dongle has been plugged in on starting up (I need to use a wired keyboard to log in), or when I plug in the dongle later. The dongle in question is the one attached at the time of the bug report (which was just after I issued the bluetooth restart command).
This is similar to Bug #762964 and #700292, but it isn't fixed yet with the latest updates installed (I believe my kernel version is the same as the kernel updates mentioned that fix it in some instances).
I also had a related problem with a logitech bluetooth dongle (for an MX5000 keyboard), where I discovered a workaround that I had to replug in the dongle while holding the red button to get it to work (I didn't try the bluetooth restart command).
I'm aware that I can just add a restart command in the rc.local file,
but I'm trying to use "stock" ubuntu, as it's now in the league of a
proper commercial OS! Let me know if you need any more info or
troubleshooting steps.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluez 4.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 3 22:28:25 2011
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: System manufacturer P5K-VM
ProcEnviron:
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=a5139a7b-604d-431d-b166-22dfc8047bfa ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to natty on 2011-04-28 (4 days ago)
dmi.bios.date: 06/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/20/2008:svnSystemmanufacturer:pnP5K-VM:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K-VM
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:83:44:57:07 ACL MTU: 384:8 SCO MTU: 64:8
UP RUNNING
RX bytes:356 acl:0 sco:0 events:13 errors:0
TX bytes:53 acl:0 sco:0 commands:13 errors:0
rfkill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/776363/+subscriptions