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 626842 - crash in Evolution Mail:
crash in Evolution Mail:
Status: RESOLVED DUPLICATE of bug 619106
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-08-13 14:07 UTC by Christoph Anton Mitterer
Modified: 2010-08-13 14:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description Christoph Anton Mitterer 2010-08-13 14:07:31 UTC
What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-fermat #1 SMP PREEMPT Tue Jul 27 21:18:47 CEST 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 717086720 vsize: 717086720 resident: 61661184 share: 23273472 rss: 61661184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1281708230 rtime: 427 utime: 376 stime: 51 cutime:29 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fc8df7fe710 (LWP 7885)]
[New Thread 0x7fc8dffff710 (LWP 7883)]
[New Thread 0x7fc8e64f3710 (LWP 7882)]
[New Thread 0x7fc8e7d5a710 (LWP 7880)]
[New Thread 0x7fc8f3887710 (LWP 7860)]
[New Thread 0x7fc8f4088710 (LWP 7859)]
0x00007fc8fe446540 in IA__g_malloc_n (n_blocks=2, n_block_bytes=4) at /tmp/buildd/glib2.0-2.24.1/glib/gmem.c:240
	in /tmp/buildd/glib2.0-2.24.1/glib/gmem.c

Thread 5 (Thread 0x7fc8e7d5a710 (LWP 7880))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.24.1/glib/gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.24.1/glib/gspawn.c line 700
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 *__GI_abort
    at abort.c line 92
  • #7 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 189
  • #8 malloc_printerr
  • #9 free_message_info_data
    at message-list.c line 4425
  • #10 IA__g_hash_table_foreach
    at /tmp/buildd/glib2.0-2.24.1/glib/ghash.c line 1325
  • #11 ml_sort_uids_by_tree
    at message-list.c line 4496
  • #12 regen_list_exec
    at message-list.c line 4736
  • #13 mail_msg_proxy
    at mail-mt.c line 471
  • #14 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.24.1/glib/gthreadpool.c line 315
  • #15 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.24.1/glib/gthread.c line 1893
  • #16 start_thread
    at pthread_create.c line 300
  • #17 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #18 ??

	Inferior 1 [process 7858] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (1695 sec old) ---------------------
7f925d79d000-7f925d79e000 rw-p 00000000 00:00 0 
7fff83dd4000-7fff83def000 rw-p 00000000 00:00 0                          [stack]
7fff83dff000-7fff83e00000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
[ConvConfHandler] isPreferred contentType: multipart/x-mixed-replace
App startup
Me TV 1.3.1
2010-08-13 15:35:15: Device: 'DiBcom 3000MC/P' (DVB-T) at "/dev/dvb/adapter0/frontend0"
2010-08-13 15:35:15: Device: 'DiBcom 3000MC/P' (DVB-T) at "/dev/dvb/adapter1/frontend0"
2010-08-13 15:35:17: Frontend::tune_to(690000000)
2010-08-13 15:35:17: Waiting for signal lock ...
2010-08-13 15:35:18: Got signal lock
2010-08-13 15:35:26: Frontend::tune_to(578000000)
2010-08-13 15:35:26: Waiting for signal lock ...
2010-08-13 15:35:27: Got signal lock
--------------------------------------------------
Comment 1 Akhil Laddha 2010-08-13 14:12:10 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 bug 619106 ***