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 493771 - crash in Evolution: trying to respond to the...
crash in Evolution: trying to respond to the...
Status: RESOLVED DUPLICATE of bug 386022
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-05 15:41 UTC by mark
Modified: 2007-11-05 18:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description mark 2007-11-05 15:41:37 UTC 
What were you doing when the application crashed?
trying to respond to the same email that has caused the last two crashes.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.16-2-686 #1 Fri Aug 18 19:01:49 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 69939200 vsize: 69939200 resident: 19308544 share: 10248192 rss: 19308544 rss_rlim: 4294967295
CPU usage: start_time: 1194277178 rtime: 408 utime: 379 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xa66436b0 (LWP 17005)]
[New Thread 0xa6541b90 (LWP 17138)]
[New Thread 0xa659eb90 (LWP 17006)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 175431

Thread 2 (Thread 0xa6541b90 (LWP 17138))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 IA__g_hash_table_foreach
    at /tmp/buildd/glib2.0-2.14.1/glib/ghash.c line 680
  • #5 e_xmlhash_foreach_key
    at e-xml-hash-utils.c line 322
  • #6 e_file_cache_get_object
    at e-file-cache.c line 318
  • #7 e_file_cache_add_object
    at e-file-cache.c line 380
  • #8 e_file_cache_replace_object
    at e-file-cache.c line 413
  • #9 e_book_backend_cache_add_contact
    at e-book-backend-cache.c line 297
  • #10 update_cache
    at e-book-backend-exchange.c line 528
  • #11 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.14.1/glib/gthread.c line 635
  • #12 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #13 clone
    from /lib/i686/cmov/libc.so.6 


----------- .xsession-errors (73 sec old) ---------------------
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(epiphany:5597): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
BBDB spinning up...
Shutting down evolution-data-server-1.10 (Evolution Calendar file and webcal backend / Evolution Addressbook file backend)
Shutting down evolution-alarm-notify (Evolution Calendar alarm notification service)
evolution-shell-Message: Killing old version of evolution-data-server...
--------------------------------------------------
Comment 1 palfrey 2007-11-05 18:11:57 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 386022 ***