Package: sasl2-bin Version: 2.1.22.dfsg1-8+etch1 Severity: critical Justification: breaks unrelated software
I ran an apt-get update after not using my machine for > 3 months, which updated (or installed) the package sasl2-bin that appears to do a /etc/init.d/saslauthd start at the end of the postinst script at /var/lib/dpkg/info/sasl2-bin.postinst. The code there is the following: # Automatically added by dh_installinit if [ -x "/etc/init.d/saslauthd" ]; then update-rc.d saslauthd defaults >/dev/null if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then invoke-rc.d saslauthd start || exit $? else /etc/init.d/saslauthd start || exit $? fi fi However, that "hangs" like this: # /etc/init.d/saslauthd start saslauthd[28763] :main : num_procs : 5 saslauthd[28763] :main : mech_option: NULL saslauthd[28763] :main : run_path : /var/run/saslauthd saslauthd[28763] :main : auth_mech : kerberos5 saslauthd[28763] :cache_alloc_mm : mmaped shared memory segment on file: /var/run/saslauthd/cache.mmap saslauthd[28763] :cache_init : bucket size: 92 bytes saslauthd[28763] :cache_init : stats size : 36 bytes saslauthd[28763] :cache_init : timeout : 28800 seconds saslauthd[28763] :cache_init : cache table: 944764 total bytes saslauthd[28763] :cache_init : cache table: 1711 slots saslauthd[28763] :cache_init : cache table: 10266 buckets saslauthd[28763] :cache_init_lock : flock file opened at /var/run/saslauthd/cache.flock saslauthd[28763] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept saslauthd[28763] :detach_tty : master pid is: 0 saslauthd[28763] :ipc_init : listening on socket: /var/run/saslauthd/mux saslauthd[28763] :main : using process model saslauthd[28764] :get_accept_lock : acquired accept lock saslauthd[28763] :have_baby : forked child: 28764 saslauthd[28763] :have_baby : forked child: 28765 saslauthd[28763] :have_baby : forked child: 28766 saslauthd[28763] :have_baby : forked child: 28767 This can only be halted by Ctrl-C, which also aborts the apt-get update. After this, apt-get requires a "dpkg --configure -a" which tries to execute the postinst script again and leaves you at the same problem. This did, in effect, break apt-get for me, since I could not use it anymore before resolving sasl problem The only workaround i found was to insert "exit 0" at the top of the postinst script. -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages sasl2-bin depends on: ii lib 2.3.6.ds1-13etch9+b1 GNU C Library: Shared libraries ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library ii lib 4.2.52+dfsg-2 Berkeley v4.2 Database Libraries [ ii lib 1.4.4-7etch7 MIT Kerberos runtime libraries ii lib 2.1.30-13.3 OpenLDAP libraries ii lib 0.79-5+etch1 Pluggable Authentication Modules l ii lib 2.1.22.dfsg1-8+etch1 Authentication abstraction library ii lib 0.9.8c-4etch9 SSL shared libraries ii lsb 3.1-23.2etch1 Linux Standard Base 3.1 init scrip sasl2-bin recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org