Bug 453337 – Crash on entering new task

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 453337 - Crash on entering new task


Summary:	Crash on entering new task


Status:	RESOLVED DUPLICATE of bug 453029

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-03 10:36 UTC by heber
Modified:	2007-08-19 16:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description heber 2007-07-03 10:36:12 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash on entering new task
Bugzilla-Product: Evolution
Bugzilla-Component: Tasks
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Evolution crashed when entering a new task in "Tasks" after switch
thereto from "Mail"

Steps to reproduce the crash:
1. Read Mails in "Mail" (with a bit of moving mails into folders)
2. Switch to Tasks via Button
3. Enter new Task in top-row field

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-data-server-1.6'

(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 46912567042896 (LWP 13163)]
[New Thread 1099184480 (LWP 13177)]
[New Thread 1074006368 (LWP 13167)]
(no debugging symbols found)
0x00002aaaacbbe0fa in waitpid () from /lib/libc.so.6

+ Trace 145426

Thread 1 (Thread 46912567042896 (LWP 13163))

#0 waitpid
from /lib/libc.so.6
#1 do_system
from /lib/libc.so.6
#2 system
from /lib/libc.so.6
#3 ??
#4 <signal handler called>
#5 g_utf8_get_char
from /usr/lib/libglib-2.0.so.0
#6 e_util_unicode_get_utf8
from /usr/lib/libedataserver-1.2.so.7
#7 e_util_utf8_strstrcasedecomp
from /usr/lib/libedataserver-1.2.so.7
#8 e_cal_backend_sexp_func_time_day_end
from /usr/lib/libedata-cal-1.2.so.1
#9 e_cal_backend_sexp_func_time_day_end
from /usr/lib/libedata-cal-1.2.so.1
#10 e_sexp_term_eval
from /usr/lib/libedataserver-1.2.so.7
#11 e_sexp_eval
from /usr/lib/libedataserver-1.2.so.7
#12 e_cal_backend_sexp_match_comp
from /usr/lib/libedata-cal-1.2.so.1
#13 e_cal_backend_file_todos_get_type
from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendfile.so
#14 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#15 e_cal_backend_file_get_type
from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendfile.so
#16 e_data_cal_view_get_type
from /usr/lib/libedata-cal-1.2.so.1
#17 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#18 ORBit_POAObject_post_invoke
from /usr/lib/libORBit-2.so.0
#19 ORBit_POAObject_post_invoke
from /usr/lib/libORBit-2.so.0
#20 giop_thread_queue_process
from /usr/lib/libORBit-2.so.0
#21 giop_thread_queue_process
from /usr/lib/libORBit-2.so.0
#22 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#24 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#25 bonobo_main
from /usr/lib/libbonobo-2.so.0
#26 ??
#27 __libc_start_main
from /lib/libc.so.6
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#0 waitpid
from /lib/libc.so.6





------- Bug created by bug-buddy at 2007-07-03 10:36 -------

Comment 1 palfrey 2007-07-03 16:48:06 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-08-19 16:28:26 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 453029 ***