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 436748 - crash in Tasks: Reading email
crash in Tasks: Reading email
Status: RESOLVED DUPLICATE of bug 427105
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 437612 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-08 00:43 UTC by David Hagood
Modified: 2007-05-28 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description David Hagood 2007-05-08 00:43:41 UTC
What were you doing when the application crashed?
Reading email


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.20-1.2925.fc7 #1 SMP Mon Feb 12 14:53:24 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 192036864 vsize: 192036864 resident: 40042496 share: 22241280 rss: 40042496 rss_rlim: 4294967295
CPU usage: start_time: 1178507146 rtime: 4409 utime: 3824 stime: 585 cutime:0 cstime: 3 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 -1208428832 (LWP 3539)]
[New Thread -1237877872 (LWP 3675)]
[New Thread -1312253040 (LWP 3674)]
[New Thread -1247700080 (LWP 3548)]
0x00550402 in __kernel_vsyscall ()

Thread 1 (Thread -1208428832 (LWP 3539))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 slab_allocator_free_chunk
    at gslice.c line 1021
  • #6 magazine_cache_push_magazine
    at gslice.c line 567
  • #7 thread_memory_magazine2_unload
    at gslice.c line 697
  • #8 IA__g_slice_free1
    at gslice.c line 806
  • #9 IA__g_slist_free_1
    at gslist.c line 59
  • #10 IA__g_slist_remove
    at gslist.c line 214
  • #11 IA__g_main_context_dispatch
    at gmain.c line 2048
  • #12 g_main_context_iterate
    at gmain.c line 2677
  • #13 IA__g_main_loop_run
    at gmain.c line 2881
  • #14 bonobo_main
    at bonobo-main.c line 311
  • #15 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (4057824 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 palfrey 2007-05-11 14:38:06 UTC
*** Bug 437612 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Kamens 2007-05-11 14:57:02 UTC
The comment in 437612 says you need more information and I should answer the questions here, but there are no questions here for me to answer.
Comment 3 Chenthill P 2007-05-11 16:45:41 UTC
(In reply to comment #2)
> The comment in 437612 says you need more information and I should answer the
> questions here, but there are no questions here for me to answer.
> 
It means that if some questions had been asked, you need to answer here as that bug is resolved as duplicate of this bug.
Comment 4 Jonathan Kamens 2007-05-11 17:32:09 UTC
That's not what the comment in the other bug said.  It said, and I quote:

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?

The "other report" referred to above is THIS one, and there are no questions in THIS report for me to answer.  For that matter, there are no questions in 437612 for me to answer either.

In short, I have no idea what information you need from me, since no one has provided me with any questions to answer.
Comment 5 Jeffrey Stedfast 2007-05-11 18:11:27 UTC
I think that other bug report comment asking you to answer questions here was just a template response.

there doesn't appear to be any questions for you to answer from my perspective either :)
Comment 6 palfrey 2007-05-28 13:15:45 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?

(More specificially, if you can duplicate this with the environment variable G_SLICE set to "debug-blocks", it might help to narrow down the actual problem)|

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