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 462248 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 461854
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-07-31 18:59 UTC by syscon
Modified: 2007-08-01 12:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description syscon 2007-07-31 18:59:47 UTC 
What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: -1782558720 vsize: -1782558720 resident: 601956352 share: 16355328 rss: 618311680 rss_rlim: 837760000
CPU usage: start_time: 1185904733 rtime: 2657 utime: 1810 stime: 847 cutime:33 cstime: 276 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47804103789776 (LWP 4753)]
[New Thread 1090525504 (LWP 5741)]
[New Thread 1124362560 (LWP 4769)]
[New Thread 1124096320 (LWP 4768)]
[New Thread 1115703616 (LWP 4767)]
[New Thread 1107310912 (LWP 4766)]
[New Thread 1098918208 (LWP 4762)]
[New Thread 1082132800 (LWP 4759)]
(no debugging symbols found)
0x00002b7a416d51f6 in poll () from /lib64/libc.so.6

+ Trace 151898

Thread 6 (Thread 1107310912 (LWP 4766))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #7 g_realloc
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #8 g_ptr_array_new
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #9 g_array_append_vals
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #10 g_byte_array_append
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #11 camel_mime_part_construct_content_from_parser
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #12 camel_mime_part_construct_from_parser
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #13 camel_multipart_new
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #14 camel_mime_part_construct_content_from_parser
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #15 camel_mime_part_construct_from_parser
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #16 camel_mime_message_new
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #17 camel_mime_part_construct_from_parser
    from /opt/gnome/lib64/libcamel-1.2.so.0
  • #18 camel_pop3_engine_new
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #19 camel_pop3_delete_old
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #20 camel_pop3_folder_new
    from /opt/gnome/lib64/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #21 camel_folder_sync
    from /opt/gnome/lib64/libcamel-provider-1.2.so.8
  • #22 mail_fetch_mail
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #23 mail_enable_stop
    from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
  • #24 e_msgport_reply
    from /opt/gnome/lib64/libedataserver-1.2.so.7
  • #25 start_thread
    from /lib64/libpthread.so.0
  • #26 clone
    from /lib64/libc.so.6
  • #27 ?? 






Comment 1


palfrey





          2007-08-01 12:32:54 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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