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 476100 - crash in Evolution: reading mail
crash in Evolution: reading mail
Status: RESOLVED DUPLICATE of bug 352284
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-09-12 06:04 UTC by daxia1015
Modified: 2007-10-20 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description daxia1015 2007-09-12 06:04:29 UTC 
What were you doing when the application crashed?
reading mail


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

Memory status: size: 1170296832 vsize: 1170296832 resident: 334254080 share: 26476544 rss: 360730624 rss_rlim: 782141440
CPU usage: start_time: 1189558450 rtime: 3594 utime: 2764 stime: 830 cutime:34 cstime: 23 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 47758961763040 (LWP 4325)]
[New Thread 1115969856 (LWP 5507)]
[New Thread 1107577152 (LWP 4400)]
[New Thread 1107310912 (LWP 4397)]
[New Thread 1098918208 (LWP 4396)]
[New Thread 1090525504 (LWP 4370)]
[New Thread 1082132800 (LWP 4367)]
0x00002b6fbea031f6 in poll () from /lib64/libc.so.6

+ Trace 162259

Thread 6 (Thread 1090525504 (LWP 4370))

  • #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


André Klapper





          2007-10-20 16:58:13 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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