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 424771 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 376826
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-31 06:28 UTC by duddumpudi.raghuram
Modified: 2007-04-12 21:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description duddumpudi.raghuram 2007-03-31 06:28:02 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: -1183776768 vsize: 0 resident: -1183776768 share: 0 rss: 667521024 rss_rlim: 0
CPU usage: start_time: 1175247737 rtime: 0 utime: 3417 stime: 0 cutime:2662 cstime: 0 timeout: 755 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233434960 (LWP 15082)]
[New Thread -1337889888 (LWP 15101)]
[New Thread -1328813152 (LWP 15096)]
[New Thread -1280312416 (LWP 15095)]
[New Thread -1288705120 (LWP 15093)]
[New Thread -1270006880 (LWP 15090)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 123744

Thread 5 (Thread -1288705120 (LWP 15093))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
    at gmessages.c line 497
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 IA__g_realloc
    at gmem.c line 172
  • #10 g_array_maybe_expand
    at garray.c line 339
  • #11 IA__g_array_append_vals
    at garray.c line 132
  • #12 IA__g_byte_array_append
    at garray.c line 653
  • #13 camel_mime_part_construct_content_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #14 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #15 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #16 camel_multipart_new
    from /usr/lib/libcamel-1.2.so.8
  • #17 camel_multipart_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #18 camel_mime_part_construct_content_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #19 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #20 camel_mime_message_new
    from /usr/lib/libcamel-1.2.so.8
  • #21 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #22 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #23 camel_data_wrapper_construct_from_stream
    from /usr/lib/libcamel-1.2.so.8
  • #24 camel_pop3_engine_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #25 camel_pop3_delete_old
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #26 camel_pop3_folder_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #27 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.8
  • #28 mail_fetch_mail
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #29 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #30 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #31 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #32 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


André Klapper





          2007-04-12 21:36:32 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 376826 ***