Bug 473941 – crash in Tasks:

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 473941 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 364700

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
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-05 15:14 UTC by andresk
Modified:	2007-09-24 17:53 UTC

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

Description andresk 2007-09-05 15:14:02 UTC

Version: 2.10

What were you doing when the application crashed?



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: 115384320 vsize: 115384320 resident: 37011456 share: 27062272 rss: 37011456 rss_rlim: 4294967295
CPU usage: start_time: 1189005208 rtime: 232 utime: 199 stime: 33 cutime:5 cstime: 11 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 -1208199456 (LWP 4403)]
[New Thread -1250952304 (LWP 4514)]
[New Thread -1238586480 (LWP 4447)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160659

Thread 1 (Thread -1208199456 (LWP 4403))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_main_context_check
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 g_main_loop_run
from /lib/libglib-2.0.so.0
#8 bonobo_main
from /usr/lib/libbonobo-2.so.0
#9 main
#0 __kernel_vsyscall



----------- .xsession-errors (13 sec old) ---------------------
C612CA9F-AC5F-4923-867F-BEEA33DDAF8D-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
B92ED6BD-38A2-41CB-A8F3-DC1CBC9776AB-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
49681F6F-40AC-4425-95A5-76C0FA7D12E2-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
203C885C-A0D0-47E8-89E1-74D4512A0C5C-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
2B20BA82-457C-468A-820F-2EE0D983E5A6-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
E1CFE9D0-9E4C-11D9-9B15-0003931A1142-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
9D669D14-7CCB-426F-8F87-1CCBCE707BDF-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
C1635027-2115-4018-AFEC-0CEC678A9B8F-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
E2B9307E-58E5-421C-8AA5-50BD7C4A28E7-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
E0ACBAF4-9E4C-11D9-9B15-0003931A1142-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
7133441C-9E4D-11D9-9B15-0003931A1142-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
870A686B-CD83-429E-A7CB-924CB74E9DD3-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
0681BAB6-EFC7-4B74-98F1-0057AE75A015-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
71578F9A-9E4D-11D9-9B15-0003931A1142-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
AC104673-3CA2-4994-8EA7-2E3DB51F0137-58B3247D-D259-4793-8468-0EAF2F5D6C1A has recurrences
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-24 17:53:46 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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