Icedove crashes with "Segmentation fault" when started from command line on
ASUS ZenBook UX32 laptop with Debian 7.8.
When started from X desktop menu the program "button" appears on the task
panel, but no Icedove window, after some seconds the button disappears.
Syslog contains the message:
kernel: [88745.510571] icedove[15673]: segfault at 7f83e070b21e ip
00007f83ee7e8f2b sp 00007ffc346eeb58 error 7 in
libc-2.13.so[7f83ee767000+181000]

Versions of the SW in use:
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64 GNU/Linux
icedove	31.8.0-1~deb7u1	amd64
libc6:amd64	2.13-38+deb7u8	amd64
libc6:i386		2.13-38+deb7u8	i386
libnss-ldap:amd64	264-2.5	amd64
libnss-mdns	0.10-3.2	amd64
ibnss-sss:amd64	1.8.4-2	amd64
libnss3:amd64	2:3.14.5-1+deb7u4	amd64
libnss3-1d:amd64	2:3.14.5-1+deb7u4	amd64
ldap-utils	2.4.31-2	amd64
libkldap4	4:4.8.4-2	amd64
libldap-2.4-2:amd64	2.4.31-2	amd64
libpam-ldap:amd64	184-8.6	amd64
libsasl2-modules-ldap:amd64	2.1.25.dfsg1-6+deb7u1	amd64
nscd		2.13-38+deb7u8	amd64

Icedove was used to read email from Office365 mail account via IMAP. For 3
months everything was fine, but suddenly Icedove started to crash. No major
software updates were done prior to that, only usual regular updates. Last
packages updated were jenkins (to 1.621), openjdk/icedtea (to
7u79-2.5.6-1~deb7u1), libexpat1 (i386 and amd64, both to 2.1.0-1+deb7u2).
i386 versions of some libraries are installed due to Skype present on the
machine.

The instructions from the page https://wiki.debian.org/Icedove, section
Debugging, were followed, files with traces are attached. There are two traces
- one with only file activity and one with full strace output. The latter shows
that the crash happens shortly after interaction with nscd, so the config for
nscd is attached also.

From the details it looks somewhat similar to the bug 703857, although the
version in the bug is much older.

Hi Yaroslav,

seems to me like a overlay of libldap and icedove's internal ldap
libary. I've seen this in earlier bug reports, but the main different is
that you've installed nscd, see:

Normally nscd fixes the symbol versioning problem. Could you try to
reinstall the previous version of icedove (you'll find it at
snapshot.debian.org[1]) and check if it's still working? If so, install
31.8.0-1~deb7u1 from oldstable-security and check again.

Cheers,
Christoph

[1] http://snapshot.debian.org/package/icedove/31.7.0-1~deb7u1/

Hej!

I tried to install Icedove both 31.7.0-1~deb7u1 and 31.2.0-1~deb7u1 - the
earliest version which does not complain about dependencies on my system.
I also tried to stop nscd to see if it makes difference.
The crash happens in the very beginning of startup, both with and without
nscd. Attached are output of strace with nscd started and stopped for 31.2
version.

When I simulated absent libldap (removing /etc/libnss-ldap.conf) Icedove was
able to start again, but it complained about unknown username. Anyway,
removing libldap completely is not an option for me. Is there any other way to
prevent Icedove to use system ldap library, as a workaround? Setting any env
variables?

Hello Yaroslav,

you try to use some prelaod magic while starting Icedove with the
LD_PRELOAD environment. Should look like this:

  $ LD_LIBRARY_PATH=/usr/lib/icedove icedove

There are old bugs that have to suggest such things if the user was in
trouble with some symbols.

Regards
Carsten

Hej!

Setting LD_LIBRARY_PATH or LD_PRELOAD did not help. What actually helped
as a workaround is
setting file ACL on /etc/libnss-ldap.conf:
setfacl -m u:<my username>:000 /etc/libnss-ldap.conf

Icedove started after that without any visible faults.

Of course this WA is only available for those who use FS which supports ACL.

Viso gero,
Yaroslav Maslennikov
mailto:yaroslav.maslennikov@tilgin.com

Привіт, мене звуть Емілія, я хочу бути вашим другом, ви говорите
англійською?

MY LOVE,
My name is Lina Williams There is my email ( linawilliams684@yahoo.com
) I pick
interest on you. I will like to speak English
with you. I will introduce myself better and send
you my picture as soon as I receive your reply.

I am looking to read from you as soon as possible.
Thanks.lL

LINA WILLIAMS