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 533298 - crash in Evolution: mandando un correo y no ...
crash in Evolution: mandando un correo y no ...
Status: RESOLVED DUPLICATE of bug 460204
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-15 14:48 UTC by malopez
Modified: 2008-05-16 05:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description malopez 2008-05-15 14:48:57 UTC 
What were you doing when the application crashed?
mandando un correo y no me lo permitio


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 144039936 vsize: 144039936 resident: 41222144 share: 21942272 rss: 41222144 rss_rlim: 4294967295
CPU usage: start_time: 1210861405 rtime: 1384 utime: 1305 stime: 79 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb682fa80 (LWP 28076)]
[New Thread 0xb26d7b90 (LWP 28105)]
[New Thread 0xb4cffb90 (LWP 28103)]
[New Thread 0xb30c9b90 (LWP 28087)]
[New Thread 0xb44feb90 (LWP 28086)]
[New Thread 0xb3cfdb90 (LWP 28084)]
[New Thread 0xb5640b90 (LWP 28081)]
[New Thread 0xb5e4ab90 (LWP 28079)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197794

Thread 1 (Thread 0xb682fa80 (LWP 28076))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libcamel-1.2.so.10
  • #11 ??
    from /usr/lib/libcamel-1.2.so.10
  • #12 ??
  • #13 <signal handler called>
  • #14 camel_header_set_param
    from /usr/lib/libcamel-1.2.so.10
  • #15 camel_content_type_set_param
    from /usr/lib/libcamel-1.2.so.10
  • #16 camel_mime_part_set_filename
    from /usr/lib/libcamel-1.2.so.10
  • #17 e_attachment_new
    from /usr/lib/evolution/2.12/libemiscwidgets.so.0
  • #18 e_attachment_bar_attach
    from /usr/lib/evolution/2.12/libemiscwidgets.so.0
  • #19 ??
    from /usr/lib/evolution/2.12/components/libevolution-mail.so
  • #20 ??
  • #21 ??
  • #22 ??
    from /usr/lib/evolution/2.12/components/libevolution-mail.so
  • #23 gtk_toggle_button_get_active
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/evolution/2.12/components/libevolution-mail.so
  • #25 ??
  • #26 ??
  • #27 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (65 sec old) ---------------------
kbuildsycoca running...
Reusing existing ksycoca
Advertencia del gestor de ventanas: La propiedad _NET_WM_NAME en la ventana 0x28005a4 contiene UTF-8 inválido
Advertencia del gestor de ventanas: La propiedad _NET_WM_ICON_NAME en la ventana 0x28005a4 contiene UTF-8 inválido
(gnome-panel:4065): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gnome-panel:4065): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
(evolution:28076): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3)
(evolution:28076): Bonobo-WARNING **: Activation exception 'No se ha podido activar «OAFIID:GNOME_Spell_Control:0.3»'
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-16 05:00:21 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 460204 ***