Bug 453421 - Evolution fails to start on x86_64
Evolution fails to start on x86_64
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
x86_64 Linux
high Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-06-30 11:02 EDT by Paul F. Johnson
Modified: 2008-07-09 04:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-09 04:55:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output from valgrind (226.99 KB, text/plain)
2008-07-01 06:32 EDT, Paul F. Johnson
no flags Details

  None (edit)
Description Paul F. Johnson 2008-06-30 11:02:57 EDT
Description of problem:
Evolution is unable to start due to a glibc problem

Version-Release number of selected component (if applicable):
glibc 2.8.90-7
glib 1.2.10-29

How reproducible:

Steps to Reproduce:
1. start evolution from either the command line or desktop icon
Actual results:
with thread apply all bt using gdb enabled
throwback gives
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffff7f9e7a0 (LWP 8146)]
CalDAV Eplugin starting up ...
** (evolution:8146): DEBUG: mailto URL command: evolution %s
** (evolution:8146): DEBUG: mailto URL program: evolution

GLib-ERROR **: gmem.c:136: failed to allocate 31740376080 bytes

Program received signal SIGTRAP, Trace/breakpoint trap
IA__g_logv (log domain=<value optimized out>, log_level=<value optimized out>,
format=<value optimized out>, args1=<value optimized out>) at gmessages.c:503
503  g_private_set(g_log_depth, GUINT_TO_POINTER(depth));

Expected results:
Evolution should start

Additional info:
Untested on x86
Comment 1 Rex Dieter 2008-06-30 11:09:38 EDT
You probably meant glib2 here.
Comment 2 Paul F. Johnson 2008-07-01 06:32:53 EDT
Created attachment 310649 [details]
Output from valgrind
Comment 3 Milan Crha 2008-07-01 06:57:35 EDT
It can be also because of broken summary file in one of your local folders. The
place where it crashed is in time of creating the folder structure and loading
message from the summary. If you try to recreate index/summary files from your
~/.evolution/mail/local directory, (and subdirectories), then there's some
chance to get this fixed. More info how to recreate summary/index files can be
found here:

Please do backup of the 'local' folder before doing anything, to be able to
return to some data when something goes wrong.

Also, the above link describes the error on an Inbox folder, but it can be in
any folder you have, from the valgrind output is not obvious which folder is in
Comment 4 Matthias Clasen 2008-07-08 11:04:26 EDT
I don't think this is a glib problem, really. 

Moving back to evolution.
Comment 5 Matthew Barnes 2008-07-08 11:25:26 EDT
I don't think it's a glibc problem either.  Looks like another 64-bit
miscalculation in libcamel.  We've seen this before with libcamel.

Paul, can you get a backtrace for this?
Comment 6 Paul F. Johnson 2008-07-08 13:59:46 EDT
I've done as in comment #3 which seems to have sorted the problem, however,
there is already a valgrind output attached to this bug, though I suspect you
need a libcamel one...
Comment 7 Matthew Barnes 2008-07-08 15:46:52 EDT
Okay, so are you still unable to start then or can the bug be closed?
Comment 8 Paul F. Johnson 2008-07-09 04:55:43 EDT
I'll close it.

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