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 437612 - crash in Tasks: Deleting messages in an ...
crash in Tasks: Deleting messages in an ...
Status: RESOLVED DUPLICATE of bug 436748
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-11 03:38 UTC by Jonathan Kamens
Modified: 2007-05-11 14:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Jonathan Kamens 2007-05-11 03:38:26 UTC 
What were you doing when the application crashed?
Deleting messages in an IMAP folder.



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.2943.fc6 #1 SMP Wed Apr 4 16:06:04 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 315768832 vsize: 315768832 resident: 43495424 share: 24047616 rss: 43495424 rss_rlim: 4294967295
CPU usage: start_time: 1178854427 rtime: 1294 utime: 1190 stime: 104 cutime:1 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 -1209190688 (LWP 27891)]
[New Thread -1211290736 (LWP 28570)]
[New Thread -1507558512 (LWP 28569)]
[New Thread -1338946672 (LWP 28145)]
[New Thread -1308705904 (LWP 27983)]
[New Thread -1295320176 (LWP 27922)]
0x00896402 in __kernel_vsyscall ()

+ Trace 133599

Thread 1 (Thread -1209190688 (LWP 27891))

  • #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 ---------------------
(evolution:27891): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:27891): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:27891): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:27891): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96aa260'
(evolution:27891): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x96aa380'
(evolution:27891): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:27891): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:27891): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:27891): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
Cannot access memory at address 0xffffffec
--------------------------------------------------
Comment 1 palfrey 2007-05-11 14:38:06 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 436748 ***