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 427105 - crash in Tasks: Reading mail in Evolutio...
crash in Tasks: Reading mail in Evolutio...
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 436748 437893 447139 448407 449130 449528 454749 457510 457875 458289 459603 460984 466185 467669 468653 468957 469792 473139 475560 477273 481316 486085 491405 495629 496107 499848 510491 517741 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-04-06 23:17 UTC by David Hagood
Modified: 2008-09-16 05:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description David Hagood 2007-04-06 23:17:25 UTC 
What were you doing when the application crashed?
Reading mail in Evolution - I wasn't even IN the tasks window


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

System: Linux 2.6.20-1.2925.fc7 #1 SMP Mon Feb 12 14:53:24 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 194383872 vsize: 194383872 resident: 45215744 share: 22970368 rss: 45215744 rss_rlim: 4294967295
CPU usage: start_time: 1175860404 rtime: 3138 utime: 2726 stime: 412 cutime:0 cstime: 4 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 -1208314144 (LWP 3556)]
[New Thread -1333912688 (LWP 7468)]
[New Thread -1237066864 (LWP 3565)]
0x00d37402 in __kernel_vsyscall ()

+ Trace 125637

Thread 2 (Thread -1333912688 (LWP 7468))

  • #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
    at pthread_mutex_lock.c line 81
  • #4 segv_redirect
    at main.c line 417
  • #5 <signal handler called>
  • #6 slab_allocator_free_chunk
    at gslice.c line 1020
  • #7 magazine_cache_push_magazine
    at gslice.c line 567
  • #8 private_thread_memory_cleanup
    at gslice.c line 665
  • #9 __nptl_deallocate_tsd
    at pthread_create.c line 153
  • #10 start_thread
    at pthread_create.c line 303
  • #11 clone
    from /lib/libc.so.6 


----------- .xsession-errors (1374224 sec old) ---------------------
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac10.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e specified for 0x2e00003 (Initializi).
--------------------------------------------------
Comment 1 Chenthill P 2007-05-09 10:33:03 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 palfrey 2007-05-28 13:14:33 UTC 
*** Bug 437893 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-05-28 13:15:45 UTC 
*** Bug 436748 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-05-28 13:19:37 UTC 
Reporters, if you can duplicate this, and get a trace with the environment variable G_SLICE set to "debug-blocks", it might help to narrow down the actual problem.
Comment 5 palfrey 2007-06-29 16:38:48 UTC 
*** Bug 449130 has been marked as a duplicate of this bug. ***
Comment 6 palfrey 2007-06-29 16:38:55 UTC 
*** Bug 449528 has been marked as a duplicate of this bug. ***
Comment 7 palfrey 2007-08-13 14:14:32 UTC 
*** Bug 466185 has been marked as a duplicate of this bug. ***
Comment 8 palfrey 2007-08-17 14:46:01 UTC 
*** Bug 444167 has been marked as a duplicate of this bug. ***
Comment 9 palfrey 2007-08-17 14:46:31 UTC 
*** Bug 448407 has been marked as a duplicate of this bug. ***
Comment 10 palfrey 2007-08-17 14:46:42 UTC 
*** Bug 454749 has been marked as a duplicate of this bug. ***
Comment 11 palfrey 2007-08-17 14:47:13 UTC 
*** Bug 467669 has been marked as a duplicate of this bug. ***
Comment 12 palfrey 2007-08-17 14:52:01 UTC 
*** Bug 457510 has been marked as a duplicate of this bug. ***
Comment 13 palfrey 2007-08-17 14:52:50 UTC 
*** Bug 460984 has been marked as a duplicate of this bug. ***
Comment 14 palfrey 2007-08-22 13:21:30 UTC 
*** Bug 468957 has been marked as a duplicate of this bug. ***
Comment 15 palfrey 2007-09-21 13:28:22 UTC 
*** Bug 469792 has been marked as a duplicate of this bug. ***
Comment 16 palfrey 2007-09-21 13:28:38 UTC 
*** Bug 468653 has been marked as a duplicate of this bug. ***
Comment 17 chris 2007-09-26 15:52:40 UTC 
is this an IMAP mailbox issue?  could it be a dup of bug 431459?
Comment 18 Basil Mohamed Gohar 2007-09-26 16:19:04 UTC 
(In reply to comment #17)
> is this an IMAP mailbox issue?  could it be a dup of bug 431459?
> 

I know that I experienced this bug, and I check one IMAP account and one POP3 account.
Comment 19 Braden 2007-09-26 20:01:37 UTC 
I check no IMAP accounts; just POP and NNTP. The bug I filed (bug 454749) was marked as a duplicate of this one.
Comment 20 palfrey 2007-10-30 11:22:15 UTC 
*** Bug 491405 has been marked as a duplicate of this bug. ***
Comment 21 Milan Crha 2007-11-15 19:14:26 UTC 
*** Bug 457875 has been marked as a duplicate of this bug. ***
Comment 22 Milan Crha 2007-11-15 19:18:15 UTC 
*** Bug 447139 has been marked as a duplicate of this bug. ***
Comment 23 Milan Crha 2007-11-15 19:20:39 UTC 
*** Bug 459603 has been marked as a duplicate of this bug. ***
Comment 24 Milan Crha 2007-11-15 19:22:23 UTC 
*** Bug 473139 has been marked as a duplicate of this bug. ***
Comment 25 Milan Crha 2007-11-15 19:23:37 UTC 
*** Bug 475560 has been marked as a duplicate of this bug. ***
Comment 26 Milan Crha 2007-11-15 19:25:17 UTC 
*** Bug 477273 has been marked as a duplicate of this bug. ***
Comment 27 Milan Crha 2007-11-15 19:25:51 UTC 
*** Bug 481316 has been marked as a duplicate of this bug. ***
Comment 28 Milan Crha 2007-11-15 19:31:19 UTC 
*** Bug 486085 has been marked as a duplicate of this bug. ***
Comment 29 Milan Crha 2007-11-15 19:44:19 UTC 
*** Bug 495629 has been marked as a duplicate of this bug. ***
Comment 30 Tobias Mueller 2007-12-04 13:32:36 UTC 
bug 501489 is different but looks similar.
Comment 31 Tobias Mueller 2007-12-04 16:13:56 UTC 
*** Bug 499848 has been marked as a duplicate of this bug. ***
Comment 32 Tobias Mueller 2007-12-04 16:41:13 UTC 
*** Bug 458289 has been marked as a duplicate of this bug. ***
Comment 33 Tobias Mueller 2007-12-04 16:59:49 UTC 
*** Bug 496107 has been marked as a duplicate of this bug. ***
Comment 34 rwarsow 2007-12-05 00:46:36 UTC 
I received an email, cause I'm a co-reporter of Bug 455690 and reporter of Bug 465655.

I don't see it any more !
Comment 35 Akhil Laddha 2008-05-19 14:57:02 UTC 
Closing as per comment#34, if you still see this issue with a current
release of evolution (2.22.x or later), please reopen. thanks in advance.
Comment 36 Milan Crha 2008-09-15 09:34:55 UTC 
*** Bug 510491 has been marked as a duplicate of this bug. ***
Comment 37 Milan Crha 2008-09-15 09:35:41 UTC 
*** Bug 517741 has been marked as a duplicate of this bug. ***