Bug 4827 - evolution-mail-CRITICAL **: e_mail_account_store_add_service: assertion `account != NULL' failed
Summary: evolution-mail-CRITICAL **: e_mail_account_store_add_service: assertion `acco...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-03-06 20:47 CET by Luan Pham
Modified: 2012-04-14 22:31 CEST (History)
2 users (show)

See Also:
Source RPM: evolution-3.3.90-3.mga2
CVE:
Status comment:


Attachments

Description Luan Pham 2012-03-06 20:47:03 CET
Description of problem: Unable to get email.
Here is an error message:
evolution-spamassassin-WARNING **: Failed to spawn SpamAssassin (/usr/bin/sa-learn --version): Failed to execute child process "/usr/bin/sa-learn" (No such file or directory)

evolution-mail-CRITICAL **: e_mail_account_store_add_service: assertion `account != NULL' failed

GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'

GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed


Version-Release number of selected component (if applicable):
3.3.90-3.mga2

How reproducible: Every time I open Evolution


Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-03-06 23:45:53 CET
Is spamassassin installed ?

Also it can be more useful to report this bug upstream at gnome

Source RPM: Evolution 3.3.90-3.mga2 (Beta 1 Release) => evolution-3.3.90-3.mga2

Remco Rijnders 2012-03-07 03:30:00 CET

CC: (none) => remco

Manuel Hiebel 2012-03-08 17:00:58 CET

Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2012-03-25 07:52:40 CEST
(In reply to comment #1)
> Is spamassassin installed ?
> 
> Also it can be more useful to report this bug upstream at gnome

@ Luan

Was it installed?

Could you please give the link to the upstream bug report?

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-04-14 22:31:12 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.