Ubuntu
evolution package

Evolution crashed after deactivating E-Mail Account in Options

Bug #70776 reported by Michael Wohlmuther
14
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Critical
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

I've deactivated an IMAP - Mailaccount in the Evolution-options and it crashed during that, after restarting the folder wasn't deactivated

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. I've forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=378451

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Unknown → Unconfirmed
Revision history for this message
Benjamin Delagoutte (benjamin-delagoutte) wrote :

My Evolution crashed after validating account changes. Is it the same bug ?

bdelagoutte@ibm-x60:~$ evolution
CalDAV Eplugin starting up ...

(evolution-2.10:14625): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one

(evolution-2.10:14625): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'

(evolution-2.10:14625): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution-2.10:14625): camel-WARNING **: camel_exception_get_id called with NULL parameter.

(evolution-2.10:14625): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
*** glibc detected *** evolution: corrupted double-linked list: 0x08853db0 ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

Benjamin, your description has not enough information to determine if that's the same problem, feel free to open a new bug with a valgrind log (https://wiki.ubuntu.com/Valgrind)

Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug should be closed in hardy, reopen if you still get the issue though

Changed in evolution:
status: Confirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Invalid → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.