Bug 2650

Summary: Crash in Evolution 2.32.2
Product: Mageia Reporter: Gene Alexander <subs>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: dmorganec, fundawang, manuel.mageia, marja11
Version: 1   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: evolution-2.32.2-2.mga1.src.rpm CVE:
Status comment:
Bug Depends on: 2721    
Bug Blocks:    
Attachments: CAMEL_DEBUG=all evolution >& evolution_debug_1.log

Description Gene Alexander 2011-09-06 23:17:48 CEST
Description of problem:

Evolution appears to be unstable following Mandriva 2010.2 to Mageia 1 migration.

(evolution:12825): camel-CRITICAL **: camel_folder_get_parent_store: assertion `CAMEL_IS_FOLDER (folder)' failed
Segmentation fault

This was not happening prior to the migration.

Version-Release number of selected component (if applicable):


How reproducible:

Unsure. Crash appears to be random.

Steps to Reproduce:
1. Migrate Mandriva 2010.2 to Mageia 1
2. Use Evolution with existing Maildir setup
3. May have random crashes
Comment 1 Manuel Hiebel 2011-09-06 23:37:49 CEST
I have update my mandriva 2010.2, for the beta2 of mageia, and I use every day evolution without crash.

To have more info from the crash you read: http://projects.gnome.org/evolution/bugs.shtml
Comment 2 Gene Alexander 2011-09-06 23:55:22 CEST
Well, I just migrated this past Sunday and have had multiple crashes with Evolution. Obviously, YMMV. :) I will try anything reasonable to resolve this. Which does not include running a beta system on my production machine.
Comment 3 Gene Alexander 2011-09-07 14:45:42 CEST
Created attachment 769 [details]
CAMEL_DEBUG=all evolution >& evolution_debug_1.log

Attached is a log while using Evolution and letting it run overnight. It crashed after I checked, read and deleted mail this morning. I was not using Evolution at the time of the crash. I had left the workspace and was working on something else. Came back to write an e-mail and Evolution had crashed. Hopefully something in this log gives someone following this bug a clue.
Comment 4 Gene Alexander 2011-09-07 15:09:34 CEST
A search on the string "camel_folder_get_parent_store" pulls up 5 hits with StartPage:

https://startpage.com/do/metasearch.pl?q=camel_folder_get_parent_store&lui=english

This one looks interesting:

http://www.go-evolution.org/Camel.Folder

But I am not a programmer, so maybe it is not helpful. If you need anything else from me, please ask.
Comment 5 Gene Alexander 2011-09-09 17:12:40 CEST
(In reply to comment #1)
> I have update my mandriva 2010.2, for the beta2 of mageia, and I use every day
> evolution without crash.
> 
> To have more info from the crash you read:
> http://projects.gnome.org/evolution/bugs.shtml

I am just curious, what is the format of your Maildir "folders". Do they use a leading dot, such as ".directory", or not? Mine do not use a leading dot as that was causing problems when I first migrated from Kmail to Evolution. I am wondering if Evolution now requires a leading dot on the primary Maildir "folders" like Kmail did.
Comment 6 Marja Van Waes 2011-11-25 14:10:26 CET
(In reply to comment #5)

> 
> I am just curious, what is the format of your Maildir "folders". Do they use a
> leading dot, such as ".directory", or not? Mine do not use a leading dot as
> that was causing problems when I first migrated from Kmail to Evolution. I am
> wondering if Evolution now requires a leading dot on the primary Maildir
> "folders" like Kmail did.

@ Manuel

Do you mind answering this question?

CC: (none) => manuel, marja11
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=2721

Marja Van Waes 2011-11-25 14:20:36 CET

Depends on: (none) => 2721

Comment 7 Manuel Hiebel 2011-11-25 14:54:29 CET
no ;)
Comment 8 Marja Van Waes 2011-11-25 15:07:55 CET
(In reply to comment #7)
> no ;)

A. No, you don't mind to answer
B. no, your folders don't have a leading dot
Or 
C. No, you don't mind to answer and no, your folders don't have a leading dot

:þ

See Also: https://bugs.mageia.org/show_bug.cgi?id=2721 => (none)

Comment 9 Marja Van Waes 2012-01-22 18:52:08 CET
cc'ing two evolution committers

CC: (none) => dmorganec, fundawang

Comment 10 Marja Van Waes 2012-04-26 21:47:48 CEST
cc'ing one more committer (there is still no maintainer)

CC: (none) => jani.valimaa

Jani Välimaa 2012-04-28 10:05:44 CEST

CC: jani.valimaa => (none)

Comment 11 Manuel Hiebel 2012-11-05 16:53:06 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 12 Manuel Hiebel 2012-12-02 14:32:30 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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