On Mon, Mar 19, 2007 at 07:57:01PM +0000, Marcos Marado wrote: > On Monday 19 March 2007 19:21, Matthew Johnson wrote: > > On Mon, Mar 19, 2007 at 05:50:48PM +0000, Marcos Marado wrote: > > > 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. > Oh, damn. I found a problem here: > [EMAIL PROTECTED]:~# cd /etc/init.d/ && ls -l blue* > lrwxrwxrwx 1 root root 9 Sep 25 21:02 bluetooth -> bluetooth > -rwxr-xr-x 1 root root 5454 Oct 9 14:55 bluetooth.dpkg-new > [EMAIL PROTECTED]:/etc/init.d# > Seems that bluetooth is a symbolic link to itself. It can't be a good thing... > > 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 > [EMAIL PROTECTED]:/etc/init.d# cd ../default/ && ls -l blue* > -rw-r--r-- 1 root root 2979 Oct 9 14:55 bluetooth > [EMAIL PROTECTED]:/etc/default# > bluez-pan does not exist. > [EMAIL PROTECTED]:/etc/default# grep EN bluetooth > BLUETOOTH_ENABLED=1 > # HIDD_ENABLED to 1. > HIDD_ENABLED=0 > DUND_ENABLED=0 > PAND_ENABLED=0 > [EMAIL PROTECTED]:/etc/default# > BLUETOOTH is enabled. > > please also check what /etc/init.d/bluetooth start does (does it start > > hcid) and what ls /etc/rc*.d/*bluetooth returns. > A symbolic link to itself? Any action will give me a "Too many levels of > symbolic links". I guess I can mv bluetooth.dpkg-new bluetooth but I won't do > it for now, I guess this might be useful to track what issued this. Well, you're not going to get any more information out of a recursive symlink than you already have. I would suggest going a head with removing the symlink and installing the .dpkg-new version in its place -- I don't see that it can hurt... Anyway, if this is the cause of the troubles, I think this bug should be reassigned to bluez-utils and downgraded. Looking at the package's maintainer scripts, it is plausible that if someone had made /etc/init.d/bluez-utils a symlink to /etc/init.d/bluetooth before upgrading, they would get this behavior. I don't know why anyone would have done this, but it does explain the symptoms. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
