After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616513 - Using Maildir I get random: Program received signal SIGSEGV, Segmentation fault
Using Maildir I get random: Program received signal SIGSEGV, Segmentation fault
Status: RESOLVED DUPLICATE of bug 545505
Product: evolution
Classification: Applications
Component: Shell
2.30.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-04-22 13:12 UTC by François Michonneau
Modified: 2010-04-23 03:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description François Michonneau 2010-04-22 13:12:16 UTC 
Hello,

  I recently switched my setup to synchronize my Gmail account to a local maildir folder using offlineimap. I run Ubuntu Lucid.

  As far as I can tell, randomly, evolution crashes. Below is the output I get from gdb. Let me know if you need additional details.

  Thanks.



Program received signal SIGSEGV, Segmentation fault.
0x0033bcd6 in ?? () from /usr/lib/libcamel-provider-1.2.so.14
(gdb) thread apply all bt

+ Trace 221512

Thread 2253 (Thread 0xab4fcb70 (LWP 6005))

  • #0 clone
    from /lib/tls/i686/cmov/libc.so.6
  • #1 ??
    from /usr/lib/libnss3.so
  • #2 ?? 






Comment 1


André Klapper





          2010-04-22 13:36:23 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!






Comment 2


François Michonneau





          2010-04-22 17:50:17 UTC
        



Program received signal SIGSEGV, Segmentation fault.
0x009f1cd6 in cfs_try_release_memory (s=0x8ad6538)
    at camel-folder-summary.c:861
861	camel-folder-summary.c: No such file or directory.
	in camel-folder-summary.c
(gdb) thread apply all bt





+
Trace
    221519






Thread 1
          (Thread 0xb7752770 (LWP 4838))


    

  • 
#0
cfs_try_release_memory

    
                at camel-folder-summary.c
                  line
                  861

    

    • 

  • 
#1
g_timeout_dispatch

    
                at /build/buildd/glib2.0-2.24.0/glib/gmain.c
                  line
                  3396

    

    • 

  • 
#2
g_main_dispatch

    
                at /build/buildd/glib2.0-2.24.0/glib/gmain.c
                  line
                  1960

    

    • 

  • 
#3
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.24.0/glib/gmain.c
                  line
                  2513

    

    • 

  • 
#4
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.24.0/glib/gmain.c
                  line
                  2591

    

    • 

  • 
#5
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.24.0/glib/gmain.c
                  line
                  2799

    

    • 

  • 
#6
bonobo_main

    
                from
                /usr/lib/libbonobo-2.so.0

    

    • 

  • 
#7
main

    
                at main.c
                  line
                  732

    

    • 







A debugging session is active.

	Inferior 1 [process 4838] will be detached.

Quit anyway? (y or n) y
Detaching from program: /usr/bin/evolution, process 4838






Comment 3


François Michonneau





          2010-04-22 17:52:25 UTC
        



I also used:
CAMEL_DEBUG=all evolution >& evolution.log

so, if necessary I can post it.

I hope I got the right kind of stack trace; if not, please let me know.

Thanks!






Comment 4


Akhil Laddha





          2010-04-23 03:39:52 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 545505 ***