Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Resolve Bluetooth headset issues after upgrade' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Resolve Bluetooth headset issues after upgrade
Authored by: alblue on Jun 04, '05 09:43:15AM
You don't need to chown it to your userid and then chown it back again; you can just edit it as root by using 'sudo'. If your favourite editor is 'pico', then you could do:
$ sudo pico blued.plist
That will allow you to edit any file (including root-owned ones. Furthermore, changing the ownership of a file will remove any sticky bits set, which although not a problem for this file may be for other ones. So it's better to get into the habit of using sudo for your editing needs...

[ Reply to This | # ]
10.4: Resolve Bluetooth headset issues after upgrade
Authored by: YuryG on Jul 11, '05 10:14:22AM

Hi All
This is a very useful post. I'm about to buy a bluetooth headset for my tiger powerbook (with bluetooth built-in).

Is there a bluetooth headset that is known to work with tiger and apple's bluetooth?

I've fiddled with Unix. But if one of you could simple spellout or typeout the entire string of commands someone needs to type in terminal to do this I'd most appreciate it. Unix newbie.

Thanks.



[ Reply to This | # ]
10.4: Resolve Bluetooth headset issues after upgrade
Authored by: vdl on Jul 20, '05 08:54:20PM

I was victim of the same problem with a Logitech Mobile Freedom headset. Worked fine with Tiger 10.4. The 10.4.2 upgrade made the headset disappear from BT altogether. Now it shows up again after repairing, but still not in the Sound Control Panel.

So in trying to follow your directions, after changing the file to XML, I get all the way to using pico to edit the blued.plist file. However, the XML has tons of lines of code following the entry naming the specific headset. So what to cut out of blued.plist and what to keep?

I also find amazing that Apple hasn't dealt with this problem with a patch of some kind --- but that's another issue. :-(
--VdL
====



[ Reply to This | # ]