Let's Sign the petition today.
Some random error messages and quick solutions... "Worked for me".. Your comments and feedback are welcome at fpiat%bigfoot.com.
You can't pair your bluetooth, you have message below in /var/log/syslog This occured to me on Debian 4.0 Etch, but it probably apply to Ubuntu and other Linux variants
Jan 7 20:05:18 hostname hcid[10063]: pin_code_request (sba=00:08:1B:00:00:01, dba=00:19:63:00:00:02) Jan 7 20:05:18 hostname hcid[10063]: call_passkey_agent(): no agent registered
That's because you don't have a passkey agent Installed. Typically you should install "bluez-passkey-gnome". (KDE might have it's own... not tested). However, if you can't want install Xwindow (on a access point..), you can quickly compile a command line passkey agent provided by package "bluez-utils".
cd /usr/share/doc/bluez-utils/examples ;gzip -dc passkey-agent.c.gz >passkey-agent.c ;apt-get install pkg-config libdbus-1-dev
Reading package lists... Done Building dependency tree... Done pkg-config is already the newest version. The following NEW packages will be installed: libdbus-1-dev 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 335kB of archives. After unpacking 803kB of additional disk space will be used. Get:1 http://ftp.fr.debian.org etch/main libdbus-1-dev 1.0.2-1 [335kB] Fetched 335kB in 0s (729kB/s) Selecting previously deselected package libdbus-1-dev. (Reading database ... 161666 files and directories currently installed.) Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.0.2-1_i386.deb) ... Setting up libdbus-1-dev (1.0.2-1) ...
make
cc `pkg-config --libs --cflags dbus-1` -DDBUS_API_SUBJECT_TO_CHANGE -DVERSION="\"0.7\"" -o passkey-agent passkey-agent.c
ls passkey-agent
-rwxr-xr-x 1 root root 15246 2007-01-07 20:19 passkey-agent
rm passkey-agent.c ;mv passkey-agent /usr/local/bin/
Then, move the file to the access-point, and run th following command (where 1234 is the PIN you want to use)
/usr/local/bin/passkey-agent --default 1234
/var/log/syslog should show
Jan 7 20:21:45 hostname hcid[10063]: name_listener_add(:1.249) Jan 7 20:21:45 hostname hcid[10063]: Default passkey agent (:1.249, /org/bluez/passkey_agent_6347) registered
You can now perform an action to associate thoses device (from another terminal), like:
obexftp -b 00:19:63:16:E6:89 -B 4 -c'Internal' -l
The phone should prompt for a PIN
This occured to me on Debian 4.0 Etch, but it probably apply to Ubuntu and other Linux variants Some command (like "id" here), returns the following error message:
id johndoe
id: ldap-nss.c:1368: do_init: Assertion `cfg->ldc_uris[__session.ls_current_uri] != ((void *)0)' failed.
That's because your system is configured to store some of it's user accounts in a ldap directory, but some configuration file isn't readable by regular user.
ls -l /etc/libnss-ldap.conf
-rw------- 1 root root 8576 Dec 5 00:31 libnss-ldap.conf
The issue is related to your installation/configuration option :
┌──────────────────────────────┤ Configuring libnss-ldap ├───────────────────────────────┐ │ │ │ If you use passwords in your libnss-ldap configuration, it is usually a good idea to │ │ have the configuration set with mode 0600 (readable and writable only by the file's │ │ owner). │ │ │ │ Note: As a sanity check, libnss-ldap will check if you have nscd installed and will │ │ only set the mode to 0600 if nscd is present. │ │ │ │ Make the configuration file readable/writeable by its owner only? │ │ │ │ <Yes> <No> │ │ │ └────────────────────────────────────────────────────────────────────────────────────────┘
The elegant want way to solve this problem is either to 1. Install nscd caching daemon, which runs as root, so it can read the file, and query ldap. or 2. If your ldap database doesn't requires to be authenticated to make a query (Debian default configuration), you can simply run dpkg-reconfigure, and anser "no", when prompted to Make the configuration file readable/writeable by its owner only? :
dpkg-reconfigure libnss-ldap
Don't simply chmod the file, as the permission are reinitialised, according to your installation preference, everytiem the package is upgraded (security update, etc).
chmod 644 /etc/libnss-ldap.conf
in syslog (or logcheck system user's mail report) :
Dec 27 04:39:54 slxmrml1 proftpd: ldap-nss.c:1376: do_init: Assertion `cfg->ldc_uris[__session.ls_current_uri] != ((void *)0)' failed.
proftpd-ldap doesn't seems to use nscd. I haven't insvestigated much on this, but it looks like a bug.
Apache 2.2 has introduced a new authentication/authorization architecture. I had some problems migrating to it.. This occured to me on Debian 4.0 Etch, but it probably apply to Ubuntu and other Linux variants
[Wed Dec 13 23:19:46 2006] [error] [client 192.168.0.1] No Authn provider configured
in /etc/apache2/apache2.conf (or /etc/apache2/site-available/YOURSITE)
#Make sure you declare a Provider avoid "No Authn provider" error message, like: AuthBasicProvider ldap
foodb.footable error : Table upgrade required. Please do "REPAIR TABLE `footable`" to fix it!
This appends to me during a mysql upgrade... you need to "repair" :
mysqlcheck --repair -A
or a little script
mysqlcheck -A > /tmp/errs cat /tmp/errs | grep -v " OK" | tr "\n\!" "\t\n" | sed -e "s/^[[:blank:]]*\([^ ]\+\)\.\([^[:blank:]]\+\).*/REPAIR TABLE \`\1\`.\`\2\`;/" | mysql -p
while upgrading uw-imapd, the installation process gets stucked
16388 pts/0 S+ 0:05 \_ /usr/bin/dpkg --status-fd 11 --unpack /var/cache/apt/archives/libvolume-id0_0.105-3_i3 16729 pts/0 S+ 0:01 \_ /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/uw-imapd.postrm up 16735 pts/0 Z+ 0:00 \_ [uw-imapd.postrm] <defunct>