On Mon, Mar 19, 2007 at 05:50:48PM +0000, Marcos Marado wrote: > [EMAIL PROTECTED]:~# ps xuaw|grep hcid > root 13625 0.0 0.0 1644 516 pts/1 R+ 17:43 0:00 grep hcid > [EMAIL PROTECTED]:~# hcid > [EMAIL PROTECTED]:~# ps xuaw|grep hcid > root 13648 0.0 0.0 1960 748 ? Ss 17:43 0:00 hcid > root 13654 0.0 0.0 1640 520 pts/1 S+ 17:43 0:00 grep hcid > [EMAIL PROTECTED]:~# > > As a matter of fact it wasn't running. Running it fixes the crash. > I have two questions here: why wasn't it running? Shouldn't kbluetoothd run > it > or at least die gracefully? I would never find out by myself that I had first > to run hcid.
This will be the problem then. hcid should be run at startup by /etc/init.d/bluetooth. This should be enabled by default. Please can you look in /etc/default/ and see whether any of the following are true: /etc/default/bluez-pan exists /etc/default/bluetooth contains BLUETOOTH_ENABLED=0 please also check what /etc/init.d/bluetooth start does (does it start hcid) and what ls /etc/rc*.d/*bluetooth returns. Matt -- Matthew Johnson
signature.asc
Description: Digital signature
