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 467669 - crash in Tasks: I wasn't even doing anyt...
crash in Tasks: I wasn't even doing anyt...
Status: RESOLVED DUPLICATE of bug 427105
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-17 14:40 UTC by Basil Mohamed Gohar
Modified: 2007-08-17 14:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Basil Mohamed Gohar 2007-08-17 14:40:08 UTC
Version: 2.10

What were you doing when the application crashed?
I wasn't even doing anything in Evolution at the time.  I had it open in the background.  All it should have been doing was checking my mail periodically.


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.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Candido-Graphite
Icon Theme: Tango

Memory status: size: 949522432 vsize: 949522432 resident: 148758528 share: 93822976 rss: 148758528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187359234 rtime: 3706 utime: 3243 stime: 463 cutime:1396 cstime: 137 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 46912496476304 (LWP 3194)]
[New Thread 1084229968 (LWP 4357)]
[New Thread 1147435344 (LWP 4356)]
[New Thread 1126189392 (LWP 4353)]
[New Thread 1136679248 (LWP 4352)]
[New Thread 1094719824 (LWP 3614)]
[New Thread 1136945488 (LWP 3222)]
[New Thread 1105209680 (LWP 3217)]
0x0000003806e0d97f in __libc_waitpid (pid=4358, stat_loc=0x7fff675235ac, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 2 (Thread 1084229968 (LWP 4357))

  • #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 1020
  • #5 magazine_cache_push_magazine
    at gslice.c line 567
  • #6 thread_memory_magazine2_unload
    at gslice.c line 697
  • #7 IA__g_slice_free_chain_with_offset
    at gslice.c line 863
  • #8 IA__g_string_chunk_free
    at gstring.c line 156
  • #9 camel_folder_search_free_result
    at camel-folder-search.c line 552
  • #10 imap_search_free
    at camel-imap-folder.c line 1702
  • #11 regen_list_exec
    at message-list.c line 3819
  • #12 mail_msg_proxy
    at mail-mt.c line 500
  • #13 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #14 g_thread_create_proxy
    at gthread.c line 594
  • #15 start_thread
    at pthread_create.c line 296
  • #16 clone
    from /lib64/libc.so.6


----------- .xsession-errors (66 sec old) ---------------------
camel-Message: --
camel-Message: --
camel-Message: --
report junk?? Dont miss our summer discounts
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(evolution:3194): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3194): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa0cac0'
(evolution:3194): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa0c8c0'
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------
Comment 1 palfrey 2007-08-17 14:47:13 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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