Reply to topic

[SOLVED] bluetooth problems after upgrading to 12.10

antoniusc
Registered Member
Posts
40
Karma
0
Hi,

I upgraded from ubuntu 12.04.02 to 12.10 (ubuntu version with kde).
After upgrade I have updated my kubuntu with this https://launchpad.net/~kubuntu-ppa/+archive/backports ppa.

The problem was that I could not deactivate bluetooth from the panel (bluedevil).
Suddently after reboot the system doesn't recognize any bluetooth adapter.

I have a desktop computer and the bluetooth adapter (integrated in my motherboard asus P8P67 PRO) was used to work fine with ubuntu 12.04 and works fine with windows 7.

here is my dmesg output:
http://pastebin.com/raw.php?i=QL9AxPuY

Last edited by antoniusc on Thu Aug 22, 2013 1:31 pm, edited 1 time in total.
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
I may have run into this issue before. I'm not sure where the blames lies exactly, but I suspect that the current Bluetooth driver does not disable the device properly, and puts it in a wedged state. To make matters worse, bluetoothd automatically restores the previous state on boot.

I have an "ASUSTek Computer, Inc. BT-253 Bluetooth Adapter" (USB ID: 0b05:1751) and this is what I had to do restore functionality:

First erase the contents of /var/lib/bluetooth/* without "bluetoothd" running.
Next, shutdown and fully power down your system (disconnect power, etc).
After 30 seconds or so, power it back up, and boot immediately into Windows. This should restore your Bluetooth adapter to functionality again.
You may now return to your Linux environment.

You will not encounter this issue as long as you do not attempt to disable the device. If you do, it is quite possible you will not be able to reactivate it, without repeating the above procedure.

It is necessary to wipe the state of /var/lib/bluetooth/* otherwise bluetoothd will restore the same "disabled" state when it starts up again, which will render it unusable again.


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
Thanks, I did that. Now I have the icon back, but it's disabled and it doesn't activate itself when I click to activate.
How to solve that?

here is new output:
Code: Select all
dmesg

http://pastebin.com/raw.php?i=zEuKa8DZ

Thank you.
antoniusc
Registered Member
Posts
40
Karma
0
now I have the problem again. I tried to terminate "bluetoothd" but I can't, it's still there.
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
Unfortunately nothing in the dmesg output was of much use i'm afraid.
For bluetoothd, you may need to try killing it more than once - make sure you use sudo to do so as bluetoothd is running as root, so regular kill commands will not work.

The first thing you should check after re-entering Linux is that your Bluetooth adapter is listed in "hcitool dev". On my system this wasn't the case before I applied the solution, and was the case afterward.


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
I can't kill it, I tried many times. What command do I have to use? I tried "term" and "kill" from kde system monitor entering my password to have root access but it's still running.
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
Weird. Can you check to see if it is the same process or if it is being respawned?
You can do this by comparing the "Process ID" of the process before and after attempting to kill it - this is available in the tooltip shown when hovering over a program in System Monitor (KSysguard).


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
bcooksley wrote:Weird. Can you check to see if it is the same process or if it is being respawned?
You can do this by comparing the "Process ID" of the process before and after attempting to kill it - this is available in the tooltip shown when hovering over a program in System Monitor (KSysguard).


I succeeded in doing what you advised following these steps to disable "bluetoothd" here: http://ubuntuusertips.wordpress.com/2012/09/21/disable-bluetoothd/.
So I rebooted (so bluetoothd was not running) and then I removed content from "/var/lib/bluetooth/*".
After that I shut down my computer and waited 1 min and then I booted in windows 7.
In there bluetooth was working fine, but after reboot in ubuntu I can see the icon (plasma panel) but I can't activate it.
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
Does "hcitool dev" list your Bluetooth adapter, and does "hcitool scan" show discoverable devices?
If they do, and you have removed the contents of /var/lib/bluetoothd/ then it is now safe to re-enable bluetoothd. This is necessary to restore the functionality of KDE's bluetooth support, which depends on bluetoothd running.


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
Are those commands? I wrote in terminal and I got:

Code: Select all
$ hcitool dev
Devices:
$ hcitool scan
Device is not available: No such device
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
Yes, they were command.

Hmm, that is concerning the bluetooth device still is not being detected. On the off chance that hcitool depends upon bluetoothd, can you make sure it is running please?


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
bcooksley wrote:Yes, they were command.

Hmm, that is concerning the bluetooth device still is not being detected. On the off chance that hcitool depends upon bluetoothd, can you make sure it is running please?


yes it's running. But sometimes the bluetooth icon is show in kde plasma panel, sometimes it's not. I don't understand why.
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
Hmm. I'm guessing that hcitool output does not differ under the root user?
If it doesn't, does your bluetooth device show up in "lsusb" and is the kernel module "btusb" loaded?


System Settings and Device Actions KCM maintainer
Image
antoniusc
Registered Member
Posts
40
Karma
0
bcooksley wrote:Hmm. I'm guessing that hcitool output does not differ under the root user?
If it doesn't, does your bluetooth device show up in "lsusb" and is the kernel module "btusb" loaded?

same result with sudo:
Code: Select all
sudo hcitool dev
[sudo]
Devices:
$ sudo hcitool scan
Device is not available: No such device

and then:
Code: Select all
lsusb | grep -i blue
Bus 002 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth


How can I check whether kernel module "btusb" is loaded?
thanks
User avatar bcooksley
Administrator
Posts
18657
Karma
83
OS
The command "lsusb" can be used to see the list of loaded kernel modules.


System Settings and Device Actions KCM maintainer
Image

 
Reply to topic

Bookmarks



Who is online

Registered users: alake, Alexa [Bot], Baidu [Spider], Bing [Bot], bshah, Exabot [Bot], Google [Bot], grubaugh, Hans, Naver Yeti [Spider], onesandzeros, orbmiser, pedrorodriguez, pvonz, searchfgold6789, Uri_Herrera, Yahoo [Bot]