Bug 449372 – crash in Tasks: selected inbox

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 449372 - crash in Tasks: selected inbox


Summary:	crash in Tasks: selected inbox


Status:	RESOLVED DUPLICATE of bug 433568

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-20 06:18 UTC by colin
Modified:	2007-06-20 08:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description colin 2007-06-20 06:18:48 UTC

What were you doing when the application crashed?
selected inbox


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:35:01 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: 145891328 vsize: 145891328 resident: 55242752 share: 21368832 rss: 55242752 rss_rlim: 4294967295
CPU usage: start_time: 1182231429 rtime: 18221 utime: 16648 stime: 1573 cutime:4604 cstime: 348 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 -1208944928 (LWP 27725)]
[New Thread -1315853424 (LWP 27742)]
[New Thread -1274033264 (LWP 27736)]
(no debugging symbols found)
0x001d8402 in __kernel_vsyscall ()

+ Trace 142339

Thread 1 (Thread -1208944928 (LWP 27725))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /usr/lib/evolution/2.10/libetable.so.0
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 e_tree_table_adapter_save_expanded_state
from /usr/lib/evolution/2.10/libetable.so.0
#8 e_tree_save_expanded_state
from /usr/lib/evolution/2.10/libetable.so.0
#9 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#10 message_list_set_folder
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#11 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#12 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#13 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#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 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib/libbonobo-2.so.0
#21 main
#0 __kernel_vsyscall



----------- .xsession-errors (61 sec old) ---------------------
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:27725): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 André Klapper 2007-06-20 08:44:08 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 433568 ***