On Wed, 2008-07-09 at 13:20 -0700, Dan Thurman wrote: >> 1) Jul 8 16:54:20 bronze hcid[8753]: Parsing /etc/bluetooth/main.conf >> failed: No such file or directory >> Jul 8 16:54:20 bronze hcid[8753]: Parsing /etc/bluetooth/input.conf >> failed: No such file or directory >> >> For the above two lines, the contents of /etc/bluetooth are: >> audio.conf hcid.conf network.conf rfcomm.conf > Why is bluetooth looking for configuration files that do not exist? Because it expects to find them. I don't know about that specific service, but it's possible on some systems to have programs look for files that they commonly use, but those files don't have to exist, and it's not a failure if they don't. It just carries on without the extra information that they would have provided. Having said that, on my system, which doesn't have any bluetooth hardware: [root@gonzales ~]# ll /etc/bluetooth/ total 32 -rw-r--r-- 1 root root 1072 2008-06-14 10:22 audio.conf -rw-r--r-- 1 root root 1231 2008-06-14 10:22 hcid.conf -rw-r--r-- 1 root root 883 2008-06-14 10:22 network.conf -rw-r--r-- 1 root root 297 2008-06-14 10:22 rfcomm.conf With the number of different problems that you've been posting about, I'm wondering if you have a knackered hard drive. -- [tim@localhost ~]$ uname -r 2.6.25.9-76.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
