Evolution Crashes while using Camel

[Mark Garrow]

For the last couple of weeks Evolution has been crashing on me daily.
1> I'm running Gutsy 7.10
2> Unknown
3> evolution:
  Installed: 2.12.1-0ubuntu1.1
  Candidate: 2.12.1-0ubuntu1.1
  Version table:
 *** 2.12.1-0ubuntu1.1 0
        500 http://us.archive.ubuntu.com gutsy-security/main Packages
        500 http://security.ubuntu.com gutsy-security/main Packages
        100 /var/lib/dpkg/status
     2.12.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com gutsy-updates/main Packages
     2.12.0-0ubuntu5 0
        500 http://us.archive.ubuntu.com gutsy/main Packages

I've started opening Evo from terminal just to view the output.. Here's what I get from the start of the program to the time I kill it.

mark@mark-desktop:~$ evolution
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
Loading Bogofilter as the default junk plugin
** (evolution:10683): DEBUG: mailto URL command: evolution %s
** (evolution:10683): DEBUG: mailto URL program: evolution
(evolution:10683): e-data-server-DEBUG: Loading categories from "/home/mark/.evolution/categories.xml"
(evolution:10683): e-data-server-DEBUG: Loaded 58 categories
BBDB spinning up...
new dimensions = (48,48)
initial setting of an image. no scaling
scale = 1

(evolution:10683): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48)
new dimensions = (48,48)
we need to scale up
scale = 1

(evolution:10683): camel-CRITICAL **: camel_store_get_folder: assertion `folder_name != NULL' failed

(evolution:10683): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:10683): evolution-mail-CRITICAL **: mail_tools_folder_to_url: assertion `CAMEL_IS_FOLDER (folder)' failed
in emp_apps_open_in
Killed
mark@mark-desktop:~$

[C de-Avillez (hggdh2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

I am not sure I follow your description: you state Evo is crashing daily, and then you state you run Evo from a terminal, and then kill it -- which is to say, it did not crash.

[Mark Garrow (scunizi)]

I will backtrace in the next day or so.. In the interim, let me clarify my initial statements. I start Evolution from the menu like most people, however when I started having problems with Evo. "graying out" and locking up (on screen, grayed, no activity, system monitor showing evo sleeping), at this point I used the terminal to start Evo so when it froze I could see the terminal messages and pass them along. I hope this clarifies things.

[Mark Garrow (scunizi)]

Here is the backtrace on the seg fault..

[Mark Garrow (scunizi)]

Should I install any evolution dbg files and redo the backtract? If so which ones? Another issue I neglected to mention previously, when starting Evo after a cold boot it automatically attempts to retrieve email from pop servers supplied by my ISP. Evo fails to connect correctly and as a result I receive popups saying that I need to re-enter my password. Doing this still does not allow Evo to connect.. You'd think that it might be something on the POP servers side. However, if I just hit cancel to all the popups and then initiate a Send/Receive it works fine.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Mark Garrow (scunizi)]

This particular issue seems to have been resolved at some point. A new issue I'll investigate and create a new bug for is Evo. freezing when left open overnight.

[Pedro Villavicencio (pedro)]

Alright, closing the bug then, thanks you.