libnss_wins.so.2 crashes after suspend to RAM

I just tried disabling the network (via the manager applet), and re-enabling it. On the re-enabling, evolution dies.

I started evolution on the console and got the following trace:

jos@roxy ~ $ evolution
** (evolution:20398): DEBUG: Loading Exchange MAPI Plugin

** (evolution:20398): DEBUG: MAPI listener is constructed with 0 listed MAPI accounts
** (evolution:20398): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:20398): DEBUG: mailto URL program: evolution
** (evolution:20398): DEBUG: EI: SHELL STARTUP
** (evolution:20398): DEBUG: EI: mail_read_notify
** (evolution:20398): DEBUG: MAIL SERVER: Count changed: 0
** (evolution:20398): DEBUG: EI: mail_read_notify
** (evolution:20398): DEBUG: MAIL SERVER: Count changed: 0
*** glibc detected *** evolution: realloc(): invalid pointer: 0x00007f58892f8970 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f5891f1dcb8]
/lib/libc.so.6(realloc+0x2bc)[0x7f5891f22f3c]
/lib/libnss_wins.so.2(Realloc+0xa6)[0x7f5872a55b37]
/lib/libnss_wins.so.2(realloc_array+0x44)[0x7f5872a55c0e]
/lib/libnss_wins.so.2(debug_add_class+0x70)[0x7f5872a3f1b7]
/lib/libnss_wins.so.2(debug_init+0x29)[0x7f5872a3f2f3]
/lib/libnss_wins.so.2(setup_logging+0x10)[0x7f5872a40118]
/lib/libnss_wins.so.2(_nss_wins_gethostbyname_r+0xd2)[0x7f587296dedc]
/lib/libnss_wins.so.2(_nss_wins_gethostbyname2_r+0x2b)[0x7f587296e364]
/lib/libc.so.6[0x7f5891f73414]
/lib/libc.so.6(getaddrinfo+0x1d2)[0x7f5891f74da2]
/usr/lib/libcamel-1.2.so.14[0x7f589aaf1e69]
/lib/libpthread.so.0[0x7f5898e443ba]
/lib/libc.so.6(clone+0x6d)[0x7f5891f8bfcd]
======= Memory map: ========
00400000-0041f000 r-xp 00000000 08:06 621719 /usr/bin/evolution
0061e000-00620000 r--p 0001e000 08:06 621719 /usr/bin/evolution
00620000-00624000 rw-p 00020000 08:06 621719 /usr/bin/evolution
00d7e000-01bb5000 rw-p 00d7e000 00:00 0 [heap]
7f5872515000-7f5872519000 r-xp 00000000 08:06 1083182 /lib/libattr.so.1.1.0
7f5872519000-7f5872718000 ---p 00004000 08:06 1083182 /lib/libattr.so.1.1.0
7f5872718000-7f5872719000 r--p 00003000 08:06 1083182 /lib/libattr.so.1.1.0
7f5872719000-7f587271a000 rw-p 00004000 08:06 1083182 /lib/libattr.so.1.1.0
7f587271a000-7f587271e000 r-xp 00000000 08:06 1083195 /lib/libcap.so.2.11
7f587271e000-7f587291d000 ---p 00004000 08:06 1083195 /lib/libcap.so.2.11
7f587291d000-7f587291e000 r--p 00003000 08:06 1083195 /lib/libcap.so.2.11
7f587291e000-7f587291f000 rw-p 00004000 08:06 1083195 /lib/libcap.so.2.11
7f587291f000-7f5872b4d000 r-xp 00000000 08:06 1083574 /lib/libnss_wins.so.2
7f5872b4d000-7f5872d4d000 ---p 0022e000 08:06 1083574 /lib/libnss_wins.so.2
7f5872d4d000-7f5872d55000 r--p 0022e000 08:06 1083574 /lib/libnss_wins.so.2
7f5872d55000-7f5872d5d000 rw-p 00236000 08:06 1083574 /lib/libnss_wins.so.2
7f5872d5d000-7f5872d5e000 rw-p 7f5872d5d000 00:00 0
7f5872d5e000-7f5872d5f000 ---p 7f5872d5e000 00:00 0
7...

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Could you try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report.?

I already attached a backtrace, was it not ok?

Anyway, here is the valgrind log.

the crash is in a winbind library

confirming the winbind cause. I de-installed winbind, and that fixed the problem for me. Sad thing is, I need the winbind for other things...

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

https://bugzilla.samba.org/show_bug.cgi?id=6712

Was wondering if you could reproduce the issue with the 3.4.0 code base (karmic/lucid) ?

still happens with latest karmic winbind (2:3.4.0-3ubuntu5.4).

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 363791 and any other logs that are relevant for this particular issue.

Sorry, I'm no longer in the position to test this.

Closing based on feedback above.

Regards
chuck