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 399553 - crash in Evolution: deleting an attachment t...
crash in Evolution: deleting an attachment t...
Status: RESOLVED DUPLICATE of bug 357492
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: 2007-01-22 21:24 UTC by Chuck Davis
Modified: 2007-01-23 13:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Chuck Davis 2007-01-22 21:24:25 UTC
What were you doing when the application crashed?
deleting an attachment to an outgoing message


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

Memory status: size: 306466816 vsize: 0 resident: 306466816 share: 0 rss: 47513600 rss_rlim: 0
CPU usage: start_time: 1169498028 rtime: 0 utime: 1932 stime: 0 cutime:1796 cstime: 0 timeout: 136 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 -1232496976 (LWP 5334)]
[New Thread -1422992480 (LWP 5599)]
[New Thread -1386222688 (LWP 5482)]
[New Thread -1377829984 (LWP 5480)]
[New Thread -1361052768 (LWP 5356)]
[New Thread -1351148640 (LWP 5353)]
[New Thread -1342362720 (LWP 5351)]
[New Thread -1333970016 (LWP 5348)]
[New Thread -1290093664 (LWP 5344)]
[New Thread -1281307744 (LWP 5343)]
[New Thread -1271850080 (LWP 5341)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232496976 (LWP 5334))

  • #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 e_attachment_bar_remove_selected
    at e-attachment-bar.c line 478
  • #6 key_press_event
    at e-msg-composer.c line 3757
  • #7 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_window_activate_key
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 bonobo_window_remove_popup
    from /usr/lib/libbonoboui-2.so.0
  • #16 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-01-23 13:59:50 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 357492 ***