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 466164 - crash in Evolution: it was idle for about 15...
crash in Evolution: it was idle for about 15...
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-08-13 08:21 UTC by rajeshwaran
Modified: 2007-08-13 14:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rajeshwaran 2007-08-13 08:21:47 UTC 
What were you doing when the application crashed?
it was idle for about 15 mins


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

Memory status: size: -1133973504 vsize: 0 resident: -1133973504 share: 0 rss: 773251072 rss_rlim: 0
CPU usage: start_time: 1186984552 rtime: 0 utime: 6771 stime: 0 cutime:5130 cstime: 0 timeout: 1641 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 -1233398096 (LWP 18505)]
[New Thread -1407190112 (LWP 23635)]
[New Thread -1354355808 (LWP 18528)]
[New Thread -1345328224 (LWP 18520)]
[New Thread -1336935520 (LWP 18519)]
[New Thread -1326998624 (LWP 18518)]
[New Thread -1282204768 (LWP 18511)]
[New Thread -1273812064 (LWP 18508)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 154817

Thread 7 (Thread -1282204768 (LWP 18511))

  • #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
    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_message_new
    from /usr/lib/libcamel-1.2.so.8
  • #16 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #17 camel_mime_part_construct_from_parser
    from /usr/lib/libcamel-1.2.so.8
  • #18 camel_data_wrapper_construct_from_stream
    from /usr/lib/libcamel-1.2.so.8
  • #19 camel_pop3_engine_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #20 camel_pop3_delete_old
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #21 camel_pop3_folder_new
    from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
  • #22 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.8
  • #23 mail_fetch_mail
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #24 mail_enable_stop
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #25 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #26 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #27 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


palfrey





          2007-08-13 14:19:37 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 ***