Bug 479122 – crash in Tasks: Quit-ing

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 479122 - crash in Tasks: Quit-ing


Summary:	crash in Tasks: Quit-ing


Status:	RESOLVED DUPLICATE of bug 455329

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-09-21 22:34 UTC by bill
Modified:	2007-09-25 02:20 UTC

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

Description bill 2007-09-21 22:34:31 UTC

Version: 2.10

What were you doing when the application crashed?
Quit-ing


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 185323520 vsize: 185323520 resident: 93597696 share: 40898560 rss: 93597696 rss_rlim: 4294967295
CPU usage: start_time: 1190375875 rtime: 10677 utime: 9932 stime: 745 cutime:1108 cstime: 176 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 -1208334624 (LWP 9552)]
[New Thread -1314153584 (LWP 12565)]
[New Thread -1282417776 (LWP 9866)]
[New Thread -1303397488 (LWP 9619)]
[New Thread -1271927920 (LWP 9595)]
[New Thread -1248928880 (LWP 9594)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164538

Thread 2 (Thread -1314153584 (LWP 12565))

#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_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib/libcamel-provider-1.2.so.10
#8 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#9 camel_folder_summary_save
from /usr/lib/libcamel-provider-1.2.so.10
#10 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
#11 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.10
#12 ??
from /usr/lib/libcamel-provider-1.2.so.10
#13 camel_store_sync
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 (36 sec old) ---------------------
(evolution:9552): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:9552): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:9552): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
JACK tmpdir identified as [/dev/shm]
(abiword:12542): libgsf:msole-CRITICAL **: ole_get_block: assertion `block < ole->info->max_block' failed
Wrong Grammar|Data Matrix:  Business_technical_specs_client_v5.|
 LowOff 0 HighOff 48 
Wrong Grammar|xls |
 LowOff 49 HighOff 52 
Wrong Grammar|Components by area and Visio document references as follows: |
 LowOff 0 HighOff 60 
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-25 02:20:20 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 455329 ***