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 367560 - crash in Evolution: trying to start a new ma...
crash in Evolution: trying to start a new ma...
Status: RESOLVED DUPLICATE of bug 360237
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-30 11:27 UTC by Colin.Cooper
Modified: 2006-11-08 17:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Colin.Cooper 2006-10-30 11:27:48 UTC
What were you doing when the application crashed?
trying to start a new mail


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 167268352 vsize: 0 resident: 167268352 share: 0 rss: 36737024 rss_rlim: 0
CPU usage: start_time: 1162207556 rtime: 0 utime: 1383 stime: 0 cutime:1178 cstime: 0 timeout: 205 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Comment 1 Karsten Bräckelmann 2006-10-30 11:36:42 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Colin.Cooper 2006-10-30 15:39:24 UTC
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 166789120 vsize: 0 resident: 166789120 share: 0 rss: 36950016 rss_rlim: 0
CPU usage: start_time: 1162222095 rtime: 0 utime: 846 stime: 0 cutime:780 cstime: 0 timeout: 66 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233193296 (LWP 16488)]
[New Thread -1358472288 (LWP 16525)]
[New Thread -1350079584 (LWP 16523)]
[New Thread -1341686880 (LWP 16522)]
[New Thread -1333294176 (LWP 16521)]
[New Thread -1324901472 (LWP 16515)]
[New Thread -1316508768 (LWP 16514)]
[New Thread -1295402080 (LWP 16513)]
[New Thread -1287009376 (LWP 16512)]
[New Thread -1278223456 (LWP 16511)]
[New Thread -1261438048 (LWP 16510)]
[New Thread -1269830752 (LWP 16495)]
[New Thread -1250604128 (LWP 16493)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233193296 (LWP 16488))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #6 emfb_search_search_activated
    at em-folder-browser.c line 1062
  • #7 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #10 IA__g_signal_emit_valist
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 emit_search_activated
    at e-search-bar.c line 161
  • #13 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #14 IA__g_closure_invoke
    at gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #16 IA__g_signal_emitv
    at gsignal.c line 2111
  • #17 gtk_binding_entry_activate
    at gtkbindings.c line 535
  • #18 binding_match_activate
    at gtkbindings.c line 955
  • #19 gtk_bindings_activate_list
    at gtkbindings.c line 1089
  • #20 IA__gtk_bindings_activate_event
    at gtkbindings.c line 1166
  • #21 gtk_widget_real_key_press_event
    at gtkwidget.c line 3655
  • #22 gtk_entry_key_press
    at gtkentry.c line 1974
  • #23 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #24 g_type_class_meta_marshal
    at gclosure.c line 567
  • #25 IA__g_closure_invoke
    at gclosure.c line 490
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #28 IA__g_signal_emit
    at gsignal.c line 2243
  • #29 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #30 IA__gtk_window_propagate_key_event
    at gtkwindow.c line 4671
  • #31 gtk_window_key_press_event
    at gtkwindow.c line 4701
  • #32 bonobo_window_remove_popup
    from /usr/lib/libbonoboui-2.so.0
  • #33 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #34 g_type_class_meta_marshal
    at gclosure.c line 567
  • #35 IA__g_closure_invoke
    at gclosure.c line 490
  • #36 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #37 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #38 IA__g_signal_emit
    at gsignal.c line 2243
  • #39 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #40 IA__gtk_propagate_event
    at gtkmain.c line 2185
  • #41 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #42 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #43 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #44 g_main_context_iterate
    at gmain.c line 2677
  • #45 IA__g_main_loop_run
    at gmain.c line 2881
  • #46 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #47 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 3 André Klapper 2006-11-08 17:41:33 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 issue has been fixed in vesion 2.8.1.1.

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