Bug 444865 – crash in Evolution: Excluindo um arquivo ".o...

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 444865 - crash in Evolution: Excluindo um arquivo ".o...


Summary:	crash in Evolution: Excluindo um arquivo ".o...


Status:	RESOLVED DUPLICATE of bug 357492

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-06 19:54 UTC by leirson.araujo
Modified:	2007-06-11 21:27 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description leirson.araujo 2007-06-06 19:54:42 UTC

What were you doing when the application crashed?
Excluindo um arquivo ".odt" anexo


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

Memory status: size: 273608704 vsize: 0 resident: 273608704 share: 0 rss: 47108096 rss_rlim: 0
CPU usage: start_time: 1181138626 rtime: 0 utime: 4275 stime: 0 cutime:4066 cstime: 0 timeout: 209 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 -1233070416 (LWP 5265)]
[New Thread -1337889888 (LWP 12852)]
[New Thread -1351328864 (LWP 12849)]
[New Thread -1328567392 (LWP 5326)]
[New Thread -1320174688 (LWP 5323)]
[New Thread -1311388768 (LWP 5322)]
[New Thread -1302996064 (LWP 5321)]
[New Thread -1294603360 (LWP 5316)]
[New Thread -1272058976 (LWP 5306)]
[New Thread -1262072928 (LWP 5295)]
[New Thread -1253643360 (LWP 5284)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 138863

Thread 1 (Thread -1233070416 (LWP 5265))

#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 André Klapper 2007-06-11 21:27:04 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 ***