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 386127 - crash in Evolution: Doing nothing, another c...
crash in Evolution: Doing nothing, another c...
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: 2006-12-15 07:57 UTC by marty
Modified: 2006-12-15 17:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description marty 2006-12-15 07:57:39 UTC 
What were you doing when the application crashed?
Doing nothing, another crash.  I thought I had fixed this problem after removing Beagle as it seemed to become more stable since then.  Obviously not.


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

Memory status: size: -1134170112 vsize: 0 resident: -1134170112 share: 0 rss: 1258377216 rss_rlim: 0
CPU usage: start_time: 1166075564 rtime: 0 utime: 4419 stime: 0 cutime:3523 cstime: 0 timeout: 896 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233041744 (LWP 12401)]
[New Thread -1404585056 (LWP 21317)]
[New Thread -1365894240 (LWP 12644)]
[New Thread -1365619808 (LWP 12622)]
[New Thread -1313829984 (LWP 12605)]
[New Thread -1297044576 (LWP 12581)]
[New Thread -1305437280 (LWP 12573)]
[New Thread -1288651872 (LWP 12559)]
[New Thread -1280259168 (LWP 12558)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 94338

Thread 7 (Thread -1305437280 (LWP 12573))

  • #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 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_realloc
    from /usr/lib/libglib-2.0.so.0
  • #10 g_ptr_array_new
    from /usr/lib/libglib-2.0.so.0
  • #11 g_array_append_vals
    from /usr/lib/libglib-2.0.so.0
  • #12 g_byte_array_append
    from /usr/lib/libglib-2.0.so.0
  • #13 camel_mime_part_construct_content_from_parser
    at camel-mime-part-utils.c line 71
  • #14 construct_from_parser
    at camel-mime-part.c line 961
  • #15 camel_mime_part_construct_from_parser
    at camel-mime-part.c line 989
  • #16 construct_from_parser
    at camel-multipart.c line 566
  • #17 camel_multipart_construct_from_parser
    at camel-multipart.c line 598
  • #18 camel_mime_part_construct_content_from_parser
    at camel-mime-part-utils.c line 119
  • #19 construct_from_parser
    at camel-mime-part.c line 961
  • #20 construct_from_parser
    at camel-mime-message.c line 590
  • #21 camel_mime_part_construct_from_parser
    at camel-mime-part.c line 989
  • #22 construct_from_stream
    at camel-mime-part.c line 1005
  • #23 camel_data_wrapper_construct_from_stream
    at camel-data-wrapper.c line 272
  • #24 pop3_get_message
    at camel-pop3-folder.c line 574
  • #25 camel_pop3_delete_old
    at camel-pop3-folder.c line 370
  • #26 pop3_sync
    at camel-pop3-folder.c line 309
  • #27 camel_folder_sync
    at camel-folder.c line 273
  • #28 fetch_mail_fetch
    at mail-ops.c line 345
  • #29 mail_msg_received
    at mail-mt.c line 570
  • #30 thread_dispatch
    at e-msgport.c line 987
  • #31 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #32 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


palfrey





          2006-12-15 17:05:49 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 352284 ***