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 560607 - crash in Evolution Mail and Calendar: receiving mails
crash in Evolution Mail and Calendar: receiving mails
Status: RESOLVED DUPLICATE of bug 338921
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-11-13 08:53 UTC by peter.bart
Modified: 2008-11-13 09:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description peter.bart 2008-11-13 08:53:13 UTC 
What were you doing when the application crashed?
receiving mails


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: SphereCrystal

Memory status: size: 100626432 vsize: 100626432 resident: 37847040 share: 19292160 rss: 37847040 rss_rlim: 4294967295
CPU usage: start_time: 1226563474 rtime: 1300 utime: 1174 stime: 126 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb66096d0 (LWP 3607)]
[New Thread 0xb2cfeb90 (LWP 5404)]
[New Thread 0xb5ca7b90 (LWP 3670)]
0xb7f71424 in __kernel_vsyscall ()

+ Trace 209723

Thread 1 (Thread 0xb66096d0 (LWP 3607))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 segv_redirect
    at main.c line 519
  • #7 <signal handler called>
  • #8 update_or_redraw
    at htmlimage.c line 1093
  • #9 html_image_factory_end_pixbuf
    at htmlimage.c line 1129
  • #10 gtk_html_stream_close
    at gtkhtml-stream.c line 137
  • #11 emhs_sync_close
    at em-html-stream.c line 140
  • #12 emss_process_message
    at em-sync-stream.c line 80
  • #13 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 4090
  • #14 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #15 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #16 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
    at main.c line 793
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6 sec old) ---------------------
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:3609): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(evolution:3607): bf-junk-filter-WARNING **: error occurred while spawning /usr/bin/bogofilter: Failed to execute child process "/usr/bin/bogofilter" (No such file or directory)
(evolution:3607): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-11-13 09:16:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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