GNOME Bugzilla – Bug 335554
libcamel1.2-6: assertion faild: (store->ostream)
Last modified: 2013-09-10 14:04:39 UTC
Steps to reproduce: 1. create an ssh tunnel to an imap server 2. create an evolution mail account that points at this local port 3. start evolution w/o this ssh tunnel running Stack trace: Unfortunately, I'm hitting another bug today that prevents me from obtaining a backtrace for this one. Other information: Originally filed as: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358067 dannf@firetheft:~$ evolution adding hook target 'source' (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. [1]+ Stopped evolution dannf@firetheft:~$ bg [1]+ evolution & dannf@firetheft:~$ (evolution:25134): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:25134): camel-WARNING **: camel_exception_get_id called with NULL parameter. camel-imap-provider-ERROR **: file camel-imap-command.c: line 180 (imap_command_start): assertion failed: (store->ostream) aborting...
which evolution and evolution-data-server versions are this exactly? can you please update to the latest versions (evo 2.4.2.1 and e-d-s 1.4.2.1) and retest? there was also one thread about this issue on the mailing list, but obviously without a solution posted: http://mail.gnome.org/archives/evolution-list/2005-October/msg00314.html
> which evolution and evolution-data-server versions are this exactly? > can you please update to the latest versions (evo 2.4.2.1 and e-d-s 1.4.2.1) > and retest? Thanks for your response, and the link to the mailing list. I am running these latest versions - Debian package versions 2.4.2.1-1 and 1.4.2.1-1 (looks like they've been in Debian since early January).
Set target milestone to 2.8
Can you test with the latest evolution stable version 2.22.3.1 and give us the back trace if still reproducible? TIA.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.24.x or later), please reopen. thanks in advance.