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 458321 - crash in Tasks: searching sent items
crash in Tasks: searching sent items
Status: RESOLVED DUPLICATE of bug 456306
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-19 15:04 UTC by Daren Grant
Modified: 2007-08-17 13:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Daren Grant 2007-07-19 15:04:48 UTC
What were you doing when the application crashed?
searching sent items


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 519811072 vsize: 519811072 resident: 26857472 share: 16863232 rss: 26857472 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184857457 rtime: 64 utime: 56 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912496447072 (LWP 3765)]
[New Thread 1147169104 (LWP 3807)]
[New Thread 1094719824 (LWP 3774)]
[New Thread 1084229968 (LWP 3772)]
(no debugging symbols found)
0x000000336360d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496447072 (LWP 3765))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 camel_message_info_ptr
    from /usr/lib64/libcamel-provider-1.2.so.10
  • #4 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #5 e_table_sorting_utils_tree_sort
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #7 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
(evolution:3720): camel-WARNING **: Cannot load summary file: `/home/dgrant/.evolution/mail/local/Inbox.ev-summary': No such file or directory
(evolution:3720): camel-groupwise-provider-WARNING **: Could not connect..failure connecting
(evolution:3720): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
CalDAV Eplugin starting up ...
** (evolution:3765): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3765): DEBUG: mailto URL program: evolution
(evolution:3765): camel-WARNING **: Cannot load summary file: `/home/dgrant/.evolution/mail/local/Inbox.ev-summary': No such file or directory
(evolution:3765): camel-groupwise-provider-WARNING **: Could not connect..failure connecting
(evolution:3765): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 palfrey 2007-08-17 13:10:23 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 456306 ***