On Monday 19 March 2007 21:02, Matthew Johnson wrote: > > Seems that bluetooth is a symbolic link to itself. It can't be a good > > thing... > > It's not a good thing and certainly isn't kdebluetooth's fault. I also > can't see anything which might cause it in bluez-utils' postinst (and > it's certainly not shipped like that) so I'm inclined to say it's a > weird local effect and not bug-worthy. Possibly you killed dpkg half-way > through an upgrade or something (as suggested by the dpkg-new. bluetooth > -> bluetooth is _still_ weird though)
I don't remember doing such thing... > > 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. > > > > What more can I do to help? > > If I were you I'd just fix it on your system either with that mv or by > removing the symlink and apt-get install --reinstall bluez-utils. Sure, I'll do that. I just wonder if the same problem happened to others... > I'm retitling the bug for the libdbus incompatibility and downgrading > the severity. If you think there is a bug here with the symlinks then > file a new one (or clone this one) against bluez-utils, but ideally only > if you can reproduce it---it's certainly is fine here and I can't > imagine it affects anyone else. Sure, I agree with that decision. Yet... [EMAIL PROTECTED]:~# rm /etc/init.d/bluetooth rm: remove symbolic link `/etc/init.d/bluetooth'? y [EMAIL PROTECTED]:~# apt-get install --reinstall bluez-utils Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0B/252kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 174589 files and directories currently installed.) Preparing to replace bluez-utils 3.7-1 (using .../bluez-utils_3.7-1_i386.deb) ... Unpacking replacement bluez-utils ... Setting up bluez-utils (3.7-1) ... Creating device nodes ... udev active, devices will be created in /dev/.static/dev/ [EMAIL PROTECTED]:~# ls /etc/init.d/bl* ls: /etc/init.d/bl*: No such file or directory [EMAIL PROTECTED]:~# Now I don't have the bluetooth init script at all! How can I fix this? And what more can I do to help solving this issue? -- Marcos Marado Sonaecom IT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
