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 400689 - crash in Evolution: Estaba abriendo una imag...
crash in Evolution: Estaba abriendo una imag...
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Bharath Acharya
Evolution QA team
: 401126 431194 451408 474858 490736 505751 509484 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-25 17:43 UTC by ubaldo.cotta
Modified: 2009-12-28 01:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ubaldo.cotta 2007-01-25 17:43:44 UTC
What were you doing when the application crashed?
Estaba abriendo una imagen que he recibido adjunta a un correo


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-12-29 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 110776320 vsize: 0 resident: 110776320 share: 0 rss: 32129024 rss_rlim: 0
CPU usage: start_time: 1169746814 rtime: 0 utime: 769 stime: 0 cutime:677 cstime: 0 timeout: 92 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231645008 (LWP 5324)]
[New Thread -1295303776 (LWP 5340)]
[New Thread -1294693472 (LWP 5339)]
[New Thread -1257038944 (LWP 5338)]
[New Thread -1266680928 (LWP 5337)]
[New Thread -1275466848 (LWP 5333)]
[New Thread -1248609376 (LWP 5330)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1231645008 (LWP 5324))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 camel_strdown
    from /usr/lib/libcamel-1.2.so.0
  • #5 em_popup_target_new_part
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #6 em_format_html_display_new
    from /usr/lib/evolution/2.8/components/libevolution-mail.so
  • #7 gtk_marshal_BOOLEAN__VOID
    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_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #20 main
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-01-25 18:57:54 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 palfrey 2007-01-27 13:38:58 UTC
*** Bug 401126 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2007-04-19 13:43:52 UTC
*** Bug 431194 has been marked as a duplicate of this bug. ***
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2007-06-17 07:52:26 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Suman Manjunath 2007-09-15 13:48:34 UTC
*** Bug 474858 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2007-12-19 03:25:57 UTC
from bug 451408:

  • #4 <signal handler called>
  • #5 camel_strdown
    at camel-string-utils.c line 103
  • #6 em_popup_target_new_part
    at em-popup.c line 301
  • #7 efhd_attachment_popup
    at em-format-html-display.c line 1491

Comment 7 André Klapper 2007-12-19 03:26:24 UTC
*** Bug 451408 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2007-12-19 03:26:27 UTC
*** Bug 490736 has been marked as a duplicate of this bug. ***
Comment 9 Milan Crha 2008-01-30 19:10:50 UTC
I would like to see the attachment header or the mail itself which causes it. It's relatively easy to prevent crash, but it's kind of workaround, so it would be better to see what kind of message causes it. Can someone of you attach here such message, or copy the beginning of image part from message source? (Ctrl+U is for message source). Thanks in advance.
Comment 10 Akhil Laddha 2008-02-11 05:34:22 UTC
*** Bug 505751 has been marked as a duplicate of this bug. ***
Comment 11 Kandepu Prasad 2008-05-26 18:01:17 UTC
*** Bug 509484 has been marked as a duplicate of this bug. ***
Comment 12 André Klapper 2009-11-07 18:05:53 UTC
NEEDINFO as per comment 9. Please provide the requested information.
Comment 13 Akhil Laddha 2009-12-28 01:43:40 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!