Bug 437893 – crash in Tasks: checking for new message...

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 437893 - crash in Tasks: checking for new message...


Summary:	crash in Tasks: checking for new message...


Status:	RESOLVED DUPLICATE of bug 427105

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-05-12 13:06 UTC by Nicolas Mailhot
Modified:	2007-05-28 13:14 UTC

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

Description Nicolas Mailhot 2007-05-12 13:06:39 UTC

What were you doing when the application crashed?
checking for new messages


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-5.mm2.fc7.nim #1 SMP Sat May 12 03:05:01 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 753270784 vsize: 753270784 resident: 65146880 share: 23437312 rss: 65146880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1178974676 rtime: 1766 utime: 1523 stime: 243 cutime:10 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47322330852720 (LWP 26504)]
[New Thread 1132755264 (LWP 26699)]
[New Thread 1082132800 (LWP 26698)]
[New Thread 1115703616 (LWP 26697)]
[New Thread 1107310912 (LWP 26611)]
[New Thread 1115969856 (LWP 26563)]
[New Thread 1090525504 (LWP 26525)]
0x00000036f840d83f in __libc_waitpid (pid=26700, stat_loc=0x7fff93f58f9c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 133791

Thread 4 (Thread 1115703616 (LWP 26697))

#0 __lll_mutex_lock_wait
from /lib64/libpthread.so.0
#1 _L_mutex_lock_103
from /lib64/libpthread.so.0
#2 __pthread_mutex_lock
at pthread_mutex_lock.c line 81
#3 <signal handler called>
#4 slab_allocator_free_chunk
at gslice.c line 1021
#5 magazine_cache_push_magazine
at gslice.c line 567
#6 private_thread_memory_cleanup
at gslice.c line 665
#7 __nptl_deallocate_tsd
at pthread_create.c line 153
#8 start_thread
at pthread_create.c line 303
#9 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
(evolution:26504): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2b0a1ab75070(0x2aaab425e850)
(evolution:26504): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:26504): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de clé « 2366D5283B29F20D »
(evolution:26504): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
warning: the debug information found in "/usr/lib/debug//usr/lib64/libhal.so.1.0.0.debug" does not match "/usr/lib64/libhal.so.1" (CRC mismatch).
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff93ffc000
--------------------------------------------------

Comment 1 palfrey 2007-05-28 13:14:33 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 427105 ***