evolution crashed with SIGSEGV in message_info_to_db()

[Brian J. Murrell]

Binary package hint: evolution

Using 2.25.92 in Jaunty.

[Pedro Villavicencio (pedro)]

Thanks for your report, it looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=574940 ; linking the report.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

This is fixed upstream now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package evolution-data-server - 2.28.3-0ubuntu1

---------------
evolution-data-server (2.28.3-0ubuntu1) lucid; urgency=low

  * New upstream version:
    Bug Fixes:
    - #602723 - Contact list name doesn't get displayed in 'To' dialog
    - #600322 - assertion failed: (reply == msg) in cs_waitinfo()
                (lp: #455020, #475147)
    - #564727 - Few memory leaks (lp: #305428)
    - #574940 - Always ref returned info from message_info_from_uid
                (lp: #341909)
    - #429317 - Use the relative URI returned if the server
                re-directs a request
    - #602820 - Test validity of a book_view before using it in LDAP
    - #590762 - Recurring google calendar items are not changeable
    - #604236 - Slow GPG processing
    - #597816 - Do not crash on incorrect parameters used in sexp to SQL
                (lp: #444177)
    - #604544 - Try Exchange fallback authentication only once
    - #600778 - Fix --enable-e2k-debug configure option resolution
    - #260407 - 'endswith' address book search doesn't work
    - #549221 - (bnc) delete, sync flags immediately
  * debian/patches/99_reconfigure.patch:
    - new version update
 -- Sebastien Bacher <email address hidden> Mon, 01 Mar 2010 22:47:15 +0100

[Brian J. Murrell (brian-interlinx)]

On Mon, 2010-03-01 at 22:20 +0000, Launchpad Bug Tracker wrote:
> This bug was fixed in the package evolution-data-server -
> 2.28.3-0ubuntu1

I beg to differ:

https://bugzilla.gnome.org/show_bug.cgi?id=574940#c101
https://bugzilla.gnome.org/show_bug.cgi?id=574940#c102

[Sebastien Bacher (seb128)]

the bugs listed in the changelog are just the bugs upstream listed in their changelog too, you can reopen if you try and still get the issue though