Bug 447044 – crash in Tasks: Started Evolution and it...

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 447044 - crash in Tasks: Started Evolution and it...


Summary:	crash in Tasks: Started Evolution and it...


Status:	RESOLVED DUPLICATE of bug 339602

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:

Duplicates:	446493 (view as bug list)
Depends on:
Blocks:

Reported:	2007-06-13 08:32 UTC by Kjartan Maraas
Modified:	2007-06-21 16:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Kjartan Maraas 2007-06-13 08:32:52 UTC

Version: 2.12

What were you doing when the application crashed?
Started Evolution and it was saving folders and summaries while fetching mail when it crashed.


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3218.fc8 #1 SMP Sat Jun 9 04:26:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 295596032 vsize: 295596032 resident: 146870272 share: 61923328 rss: 146870272 rss_rlim: 4294967295
CPU usage: start_time: 1181723360 rtime: 2268 utime: 1693 stime: 575 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208351008 (LWP 3481)]
[New Thread -1349383280 (LWP 3536)]
[New Thread -1328010352 (LWP 3513)]
[New Thread -1317520496 (LWP 3506)]
0x0012d402 in __kernel_vsyscall ()

+ Trace 140582

Thread 2 (Thread -1349383280 (LWP 3536))

#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 segv_redirect
at main.c line 422
#5 <signal handler called>
#6 camel_index_add_name
at camel-index.c line 183
#7 camel_folder_summary_info_new_from_parser
at camel-folder-summary.c line 1017
#8 camel_folder_summary_add_from_parser
at camel-folder-summary.c line 922
#9 summary_update
at camel-mbox-summary.c line 485
#10 mbox_summary_check
at camel-mbox-summary.c line 572
#11 camel_local_summary_check
at camel-local-summary.c line 268
#12 local_refresh_info
at camel-local-folder.c line 475
#13 camel_folder_refresh_info
at camel-folder.c line 302
#14 refresh_folder_exec
at mail-ops.c line 1534
#15 mail_msg_proxy
at mail-mt.c line 491
#16 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#17 g_thread_create_proxy
at gthread.c line 591
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors (36 sec old) ---------------------
(evolution:3481): camel-WARNING **: Could not find key entry for word 'pixbufloader': Ugyldig fildeskriptor
(evolution:3481): camel-WARNING **: Could not find key entry for word '0xd0000000': Ugyldig eller ufullstendig multibyte eller bredt tegn
(evolution:3481): e-data-server-WARNING **: Could not open converter for 'X-UNKNOWN' to 'UTF-8' charset
(evolution:3481): camel-WARNING **: Could not find key entry for word '0000000040000000': Ugyldig argument
(evolution:3481): camel-WARNING **: Could not find key entry for word '0x000000003ff30000': Ugyldig argument
Couldn't open sftp://kmaraas@window.gnome.org:22/home/users/kmaraas/public_html/calendar.ics: Tidsavbrudd nådd
--------------------------------------------------

Comment 1 André Klapper 2007-06-15 15:55:34 UTC

*** Bug 446493 has been marked as a duplicate of this bug. ***

Comment 2 André Klapper 2007-06-21 16:22:35 UTC

same issue as bug 339602.

*** This bug has been marked as a duplicate of 339602 ***