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 427211 - crash in Evolution: I was just composing an ...
crash in Evolution: I was just composing an ...
Status: RESOLVED DUPLICATE of bug 417440
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-04-07 09:00 UTC by Sven J.
Modified: 2007-04-07 09:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sven J. 2007-04-07 09:00:45 UTC 
What were you doing when the application crashed?
I was just composing an email and had 4 files attached. Then i decided to remove those 4 attachments again.
I draw an frame arround the 4 files and pressed the del key. I was wondering that only one file was removed. I repeated this until the last file should be removed, but when pressing the del key while the last file was marked - evolution crashed.



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

Memory status: size: 292659200 vsize: 0 resident: 292659200 share: 0 rss: 47239168 rss_rlim: 0
CPU usage: start_time: 1175934046 rtime: 0 utime: 2516 stime: 0 cutime:2208 cstime: 0 timeout: 308 it_real_value: 0 frequency: 11

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 -1233471824 (LWP 4899)]
[New Thread -1426023520 (LWP 6005)]
[New Thread -1368286304 (LWP 6003)]
[New Thread -1376679008 (LWP 4918)]
[New Thread -1312879712 (LWP 4913)]
[New Thread -1321366624 (LWP 4911)]
[New Thread -1304487008 (LWP 4909)]
[New Thread -1295303776 (LWP 4908)]
[New Thread -1286911072 (LWP 4907)]
[New Thread -1278518368 (LWP 4906)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 125731

Thread 1 (Thread -1233471824 (LWP 4899))

  • #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 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_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_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_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 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-04-07 09:53:17 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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