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 451404 - crash in Tasks: There is an email that c...
crash in Tasks: There is an email that c...
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-26 21:27 UTC by huixquic
Modified: 2007-07-26 21:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description huixquic 2007-06-26 21:27:29 UTC
Version: 2.10

What were you doing when the application crashed?
There is an email that crashes Evolution...don't know that email characteristics yet except it is formated with HTML


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 182611968 vsize: 182611968 resident: 75530240 share: 29929472 rss: 75530240 rss_rlim: 4294967295
CPU usage: start_time: 1182892963 rtime: 7119 utime: 5264 stime: 1855 cutime:70 cstime: 29 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208961312 (LWP 22050)]
[New Thread -1274844272 (LWP 22146)]
[New Thread -1264354416 (LWP 22144)]
[New Thread -1242981488 (LWP 22135)]
[New Thread -1285882992 (LWP 22092)]
[New Thread -1253471344 (LWP 22088)]
[New Thread -1232491632 (LWP 22085)]
(no debugging symbols found)
0x00c92402 in __kernel_vsyscall ()

Thread 4 (Thread -1242981488 (LWP 22135))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #7 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #10 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #11 camel_local_summary_check
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #12 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #13 camel_folder_refresh_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6


----------- .xsession-errors (420626 sec old) ---------------------
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
fixme:actctx:ReleaseActCtx 0xf00baa
report junk?? Conferencia - Atención telefónica
(evolution:6498): libebook-WARNING **: invalid escape, passing it through
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-06-27 13:31:32 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-07-26 21:50:16 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 339602 ***