I'm not sure it was necessarily an update that fixed the problem, though since I had been using Pidgin with skype4pidgin for some time before the crash without problems, and have continued using it regularly since with no problems, it is certainly plausible that the crash was a bug introduced with an update to some package, and then fixed with another update.
In any case, I have since installed libc6-dbg and pidgin-skype-dbg, so if I do experience this bug again, there's a much better chance that the stack trace from Apport would be usable. I do have two questions as to what I should do if this bug (or a similar situation with pidgin) occurs again: (1) If the automatic stack trace attached by Apport to the bug report is good, should I still reproduce it with Valgrind and attach the log? (2) Should I open a new bug report, or reopen this one (changing its status to New)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/623139 Title: pidgin assert failure: *** glibc detected *** pidgin: munmap_chunk(): invalid pointer: 0x0000000002fe8460 *** -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
