Bug 482344 – crash in Tasks: Configurando el tiempo d...

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 482344 - crash in Tasks: Configurando el tiempo d...


Summary:	crash in Tasks: Configurando el tiempo d...


Status:	RESOLVED DUPLICATE of bug 433922

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-01 19:25 UTC by eduvera
Modified:	2007-10-02 03:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description eduvera 2007-10-01 19:25:24 UTC

Version: 2.10

What were you doing when the application crashed?
Configurando el tiempo de recepción de e-mail's


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136671232 vsize: 136671232 resident: 53780480 share: 38006784 rss: 53780480 rss_rlim: 4294967295
CPU usage: start_time: 1191246809 rtime: 1584 utime: 1445 stime: 139 cutime:52 cstime: 14 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209125152 (LWP 2697)]
[New Thread -1334850672 (LWP 15449)]
[New Thread -1260881008 (LWP 2774)]
[New Thread -1271764080 (LWP 2744)]
[New Thread -1219929200 (LWP 2719)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166935

Thread 1 (Thread -1209125152 (LWP 2697))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 pango_attr_list_unref
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libgtkhtml-3.14.so.19
#12 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#13 ??
from /usr/lib/libgtkhtml-3.14.so.19
#14 ??
from /usr/lib/libgtkhtml-3.14.so.19
#15 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#16 ??
from /usr/lib/libgtkhtml-3.14.so.19
#17 ??
from /usr/lib/libgtkhtml-3.14.so.19
#18 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#19 ??
from /usr/lib/libgtkhtml-3.14.so.19
#20 g_object_unref
from /lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtkhtml-3.14.so.19
#22 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib/libgobject-2.0.so.0
#25 ??
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#27 g_signal_emit
from /lib/libgobject-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#31 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#39 ??
from /lib/libgobject-2.0.so.0
#40 g_closure_invoke
from /lib/libgobject-2.0.so.0
#41 ??
from /lib/libgobject-2.0.so.0
#42 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#43 g_signal_emit
from /lib/libgobject-2.0.so.0
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 g_object_unref
from /lib/libgobject-2.0.so.0
#47 ??
from /lib/libgobject-2.0.so.0
#48 g_value_unset
from /lib/libgobject-2.0.so.0
#49 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#50 g_signal_emit
from /lib/libgobject-2.0.so.0
#51 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgtkhtml-3.14.so.19
#53 ??
from /usr/lib/libgtkhtml-3.14.so.19
#54 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#55 ??
from /usr/lib/libgtkhtml-3.14.so.19
#56 ??
from /usr/lib/libgtkhtml-3.14.so.19
#57 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#58 ??
from /usr/lib/libgtkhtml-3.14.so.19
#59 ??
from /usr/lib/libgtkhtml-3.14.so.19
#60 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#61 ??
from /usr/lib/libgtkhtml-3.14.so.19
#62 ??
from /usr/lib/libgtkhtml-3.14.so.19
#63 html_object_destroy
from /usr/lib/libgtkhtml-3.14.so.19
#64 html_engine_parse
from /usr/lib/libgtkhtml-3.14.so.19
#65 gtk_html_begin_full
from /usr/lib/libgtkhtml-3.14.so.19
#66 gtk_html_begin
from /usr/lib/libgtkhtml-3.14.so.19
#67 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#68 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#69 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#70 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#71 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#72 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#73 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#74 ??
from /lib/libglib-2.0.so.0
#75 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#76 ??
from /lib/libglib-2.0.so.0
#77 g_main_loop_run
from /lib/libglib-2.0.so.0
#78 bonobo_main
from /usr/lib/libbonobo-2.so.0
#79 main
#0 __kernel_vsyscall

Comment 1 Tobias Mueller 2007-10-02 03:44:48 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 433922 ***