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 418530 - crash in Evolution: Trying To delete an atta...
crash in Evolution: Trying To delete an atta...
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-03-15 11:17 UTC by danny.webb
Modified: 2007-03-15 15:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description danny.webb 2007-03-15 11:17:27 UTC
What were you doing when the application crashed?
Trying To delete an attachment from an email.


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

Memory status: size: 309813248 vsize: 0 resident: 309813248 share: 0 rss: 40992768 rss_rlim: 0
CPU usage: start_time: 1173955851 rtime: 0 utime: 2196 stime: 0 cutime:2044 cstime: 0 timeout: 152 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 -1233484112 (LWP 19591)]
[New Thread -1410237536 (LWP 20006)]
[New Thread -1400898656 (LWP 20004)]
[New Thread -1391096928 (LWP 19725)]
[New Thread -1374311520 (LWP 19620)]
[New Thread -1365525600 (LWP 19615)]
[New Thread -1357132896 (LWP 19614)]
[New Thread -1348740192 (LWP 19611)]
[New Thread -1302209632 (LWP 19609)]
[New Thread -1293816928 (LWP 19608)]
[New Thread -1285424224 (LWP 19603)]
[New Thread -1275966560 (LWP 19602)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233484112 (LWP 19591))

  • #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
    at gtkmarshalers.c line 84
  • #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
    at gsignal.c line 2209
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #13 IA__gtk_window_propagate_key_event
    at gtkwindow.c line 4671
  • #14 gtk_window_key_press_event
    at gtkwindow.c line 4701
  • #15 bonobo_window_remove_popup
    from /usr/lib/libbonoboui-2.so.0
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #17 g_type_class_meta_marshal
    at gclosure.c line 567
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #23 IA__gtk_propagate_event
    at gtkmain.c line 2185
  • #24 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #25 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #27 g_main_context_iterate
    at gmain.c line 2677
  • #28 IA__g_main_loop_run
    at gmain.c line 2881
  • #29 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #30 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 1 Susana 2007-03-15 15:32:02 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 357492 ***