[Dovecot] Problems after upgrade (0.99.x -> 1.0.x)

[websafe]

Matthias Andree wrote::
 > fazer69#o2.pl writes:
 >> dovecot: Dovecot v1.0.rc6 starting up
 >> dovecot: Login process died too early - shutting down
 >> dovecot: child 15288 (login) killed with signal 11
 >> dovecot: child 15289 (login) killed with signal 11
 >> dovecot: child 15290 (login) killed with signal 11
 >> How can I get the new Dovecot acting as the old one?
 > Does this reproduce after a reboot? If so, get a stack backtrace from
 > the core file or by attaching a debugger such as GDB and post it.

Yes, after reboot it was the same. When I now start Dovecot,
simply by typing:

dovecot

Aug 15 23:45:30 phazer dovecot: Dovecot v1.0.rc6 starting up
Aug 15 23:45:32 phazer dovecot: Login process died too early - shutting down
Aug 15 23:45:32 phazer dovecot: imap-login: Panic: Leaked file fd 5: dev 0.10 inode 5
Aug 15 23:45:32 phazer last message repeated 2 times
Aug 15 23:45:32 phazer dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.10 inode 5
Aug 15 23:45:32 phazer dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.10 inode 5
Aug 15 23:45:32 phazer dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 inode 5
Aug 15 23:45:32 phazer dovecot: child 10139 (auth) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10140 (login) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10142 (login) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10143 (login) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10144 (login) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10141 (login) killed with signal 6
Aug 15 23:45:32 phazer dovecot: child 10145 (login) killed with signal 6

Still this error, but :> that's why I run it for now using:

LD_LIBRARY_PATH=/usr/lib/dovecot/:/usr/lib/dovecot/imap/ dovecot

Aug 15 23:48:44 phazer dovecot: Dovecot v1.0.rc6 starting up
Aug 15 23:48:53 phazer dovecot: imap-login: Login: user=<websafe>, method=plain, \
	rip=*, lip=*

(see my previus posting)

So IMHO sth is wrong with "my" libz :-)
But a I mentioned,  it works fine prefixed with LD_LIBRARY_PATH...

:)