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 367007 - crash in Evolution: deleting a search folder...
crash in Evolution: deleting a search folder...
Status: RESOLVED DUPLICATE of bug 580820
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-29 17:00 UTC by wsfulmer
Modified: 2009-05-28 06:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description wsfulmer 2006-10-29 17:00:32 UTC
What were you doing when the application crashed?
deleting a search folder that pointed to some newsgroups


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

Memory status: size: 178511872 vsize: 0 resident: 178511872 share: 0 rss: 69181440 rss_rlim: 0
CPU usage: start_time: 1162141100 rtime: 0 utime: 2230 stime: 0 cutime:2104 cstime: 0 timeout: 126 it_real_value: 0 frequency: 3

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232730448 (LWP 6326)]
[New Thread -1330250848 (LWP 6366)]
[New Thread -1329984608 (LWP 6359)]
[New Thread -1273148512 (LWP 6358)]
[New Thread -1319507040 (LWP 6350)]
[New Thread -1311114336 (LWP 6349)]
[New Thread -1302721632 (LWP 6348)]
[New Thread -1281631328 (LWP 6343)]
[New Thread -1264718944 (LWP 6337)]
[New Thread -1256326240 (LWP 6336)]
[New Thread -1247880288 (LWP 6335)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Comment 1 André Klapper 2006-10-30 01:07:35 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 wsfulmer 2006-10-30 01:50:42 UTC
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 159248384 vsize: 0 resident: 159248384 share: 0 rss: 65875968 rss_rlim: 0
CPU usage: start_time: 1162172897 rtime: 0 utime: 770 stime: 0 cutime:750 cstime: 0 timeout: 20 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 -1232537936 (LWP 28482)]
[New Thread -1309820000 (LWP 28504)]
[New Thread -1272919136 (LWP 28503)]
[New Thread -1281311840 (LWP 28502)]
[New Thread -1289741408 (LWP 28497)]
[New Thread -1264526432 (LWP 28493)]
[New Thread -1256133728 (LWP 28492)]
[New Thread -1247687776 (LWP 28491)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232537936 (LWP 28482))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 ??
  • #6 camel_message_info_ptr
    at camel-folder-summary.c line 2966
  • #7 vee_info_ptr
    at camel-vee-summary.c line 65
  • #8 camel_message_info_ptr
    at camel-folder-summary.c line 2966
  • #9 ml_tree_value_at
    at message-list.c line 1411
  • #10 etmc_value_at
    at e-tree-memory-callbacks.c line 104
  • #11 e_tree_model_value_at
    at e-tree-model.c line 783
  • #12 etta_value_at
    at e-tree-table-adapter.c line 613
  • #13 e_table_model_value_at
    at e-table-model.c line 130
  • #14 ect_real_get_text
    at e-cell-text.c line 250
  • #15 e_cell_text_get_text
    at e-cell-text.c line 227
  • #16 generate_layout
    at e-cell-text.c line 652
  • #17 ect_height
    at e-cell-text.c line 1150
  • #18 e_cell_height
    at e-cell.c line 331
  • #19 ecv_height
    at e-cell-hbox.c line 211
  • #20 e_cell_height
    at e-cell.c line 331
  • #21 ecv_draw
    at e-cell-vbox.c line 146
  • #22 e_cell_draw
    at e-cell.c line 277
  • #23 eti_draw
    at e-table-item.c line 2001
  • #24 gnome_canvas_root
    from /usr/lib/libgnomecanvas-2.so.0
  • #25 gnome_canvas_item_new
    from /usr/lib/libgnomecanvas-2.so.0
  • #26 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #32 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gdk_window_is_viewable
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #36 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #37 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #41 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #42 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 3 André Klapper 2006-10-30 02:36:20 UTC
stacktrace looks very good, confirming. thanks!
Comment 4 Akhil Laddha 2009-05-28 06:04:58 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 580820 ***