You are not logged in.
Pages: 1
Hey,
I have a Problem with Bluetooth on my MacBook Pro (7,1) running Arch / KDE.
When i disable bluetooth and resart the bluetooth daemon (/etc/rc.d/bluetooth restart),
bluetooth won't work anymore.
The bluetooth icon is still in the there, but it wont work anymore.
Neither does disabeling work, nor does it connect with or see any bluetooth devices.
rm -rf /var/lib/bluetooth
and restarting bluetooth again (/etc/rc.d/bluetooth restart) does actually help, but just as long as
i disable BT and reboot.
Note: In the past BT worked without this issue, and disabeling and reenabeling it without reboot works too!
Last edited by markus2107 (2012-08-01 08:14:55)
Offline
I think i have tracked down the problem:
- when BT is disabled and i reboot (or restart the BT daemon) the /var/lib/bluetooth10\:9A\:DD\:CE\:0E\:71/config file looks like this:
name MacBookArch-0
mode off
onmode connectable- if BT is enabled ot mode is set to "connectable"
- so i looks like the applet doesn't get it, that BT is disabled and i cannot enable it (and therefore also not disable it)
- is there a way to set mode to "connectable" on every shutdown and to disable BT on every time i boot. As some kind of a workaround?
- what could cause this problem?
EDIT:
Maybe a
sudo hciconfig hci0 up
sudo hciconfig hci0 downwould help. I tried it out right now, and this would solve my problem. So is there a way to execute this command on every time i boot?
EDIT2:
As a workaround i created ~/.kde4/Autostart/bluetooth.sh (marked as executable)
#! /bin/bash
sleep 7
sudo hciconfig hci0 up
sudo hciconfig hci0 down
# End of filebut it doesn't really do what i want. Am i doing something wrong? Has anybody an other solution for my problem?
Would anybody answer, please?
Last edited by markus2107 (2012-07-30 09:10:41)
Offline
For some days now, im trying to get out how to fix my problem.
PLEASE, could someone help?
If no one else had such a problem before: What config files / packages could i delete / reinstall to try to get rid of this bug?
I realy know what the problem is: When i disable BT via bluedevil, "mode" in /var/lib/bluetooth/10:9A:DD:CE:0E:71/config is set to "off".
And when bluedevil starts and mode in the config file is set "off" it isn't able to control BT. If i delete the file, or set mode to "connectable" it works.
could someone please look for his /var/blib/bluetooth/aa:bb:cc:dd:ee:ff:/config and look, wheather mode is set off, when disabling bt via bluedevil,
and see if bluedevil works, if you restart it with mode "off"?
Offline
hey, so... the tray not working (even after a reboot), since like two months ago was also bugging me, and i gave it a go:
daemon not running
daemon off daemon on
wireless led /var/lib/bluetooth/*/config hci0 state tray reports hci0 state /var/lib/bluetooth/*/config tray works?
on off up off down off yes
on off down on down off no
on connectable down on up connectable yes
on connectable up on up connectable yes
off off no such device no tray no such device off no tray
off connectable no such device no tray no such device connectable no tray
daemon running
wireless led off wireless led indicator on
off no such device on down off no
connectable no such device on up connectable yesbasically, turning off the device through the tray turns /var/lib/bluetooth/*/config's mode to off, which renders it useless if the daemon restarts; while having it always on connectable gives you no trouble at all (as far as i can see).
also... if the tray is not working, bringing the interface up manually (which also turns on the /var/lib... config) solves the issue.
so... i'm thinking of setting an inmutable attribute on it, tho i haven't tested it
Offline
ok, so that seems to work alright.
now, that would start the pc with bluetooth up if the device is powered on (i actually don't have separate switches for bluetooth and wifi so i can't help it)
but since that's not what i want (and neither do you i suspect) (power savings and all) what i did was to add:
hciconfig hci0 downto my /etc/rc.local,
so there.
p.s.: i think a bug report is in order, can anyone comment if this is reproducible on their machines and/or an arch specific issue?
Offline
Pages: 1