Bug 463420 – crash in Tasks: configurando as preferen...

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 463420 - crash in Tasks: configurando as preferen...


Summary:	crash in Tasks: configurando as preferen...


Status:	RESOLVED DUPLICATE of bug 438529

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
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-08-04 13:32 UTC by andersonbeatriz
Modified:	2007-08-10 18:49 UTC

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

Description andersonbeatriz 2007-08-04 13:32:24 UTC

Version: 2.10

What were you doing when the application crashed?
configurando as preferencias do evolution


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 129740800 vsize: 129740800 resident: 59355136 share: 34594816 rss: 59355136 rss_rlim: 4294967295
CPU usage: start_time: 1186232468 rtime: 3344 utime: 3098 stime: 246 cutime:139 cstime: 44 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 -1208375584 (LWP 2961)]
[New Thread -1231365232 (LWP 3035)]
[New Thread -1220265072 (LWP 2998)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 152775

Thread 1 (Thread -1208375584 (LWP 2961))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_slist_remove
from /lib/libglib-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_window_remove_accel_group
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libbonoboui-2.so.0
#10 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_container_forall
from /usr/lib/libgtk-x11-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 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 g_cclosure_marshal_VOID__OBJECT
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 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#47 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#48 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgtk-x11-2.0.so.0
#53 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#54 ??
from /lib/libgobject-2.0.so.0
#55 g_closure_invoke
from /lib/libgobject-2.0.so.0
#56 ??
from /lib/libgobject-2.0.so.0
#57 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#58 g_signal_emit
from /lib/libgobject-2.0.so.0
#59 ??
from /usr/lib/libgtk-x11-2.0.so.0
#60 ??
from /usr/lib/libgtk-x11-2.0.so.0
#61 ??
from /usr/lib/libgtk-x11-2.0.so.0
#62 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#63 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#64 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#65 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#66 g_cclosure_marshal_VOID
from /lib/libgobject-2.0.so.0
#67 ??
from /lib/libgobject-2.0.so.0
#68 g_closure_invoke
from /lib/libgobject-2.0.so.0
#69 ??
from /lib/libgobject-2.0.so.0
#70 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#71 g_signal_emit
from /lib/libgobject-2.0.so.0
#72 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#73 ??
from /usr/lib/libgtk-x11-2.0.so.0
#74 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#75 g_closure_invoke
from /lib/libgobject-2.0.so.0
#76 ??
from /lib/libgobject-2.0.so.0
#77 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#78 g_signal_emit
from /lib/libgobject-2.0.so.0
#79 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#80 ??
from /usr/lib/libgtk-x11-2.0.so.0
#81 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#82 ??
from /lib/libgobject-2.0.so.0
#83 g_closure_invoke
from /lib/libgobject-2.0.so.0
#84 ??
from /lib/libgobject-2.0.so.0
#85 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#86 g_signal_emit
from /lib/libgobject-2.0.so.0
#87 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#88 ??
from /usr/lib/libgtk-x11-2.0.so.0
#89 ??
from /usr/lib/libgtk-x11-2.0.so.0
#90 ??
from /lib/libgobject-2.0.so.0
#91 g_closure_invoke
from /lib/libgobject-2.0.so.0
#92 ??
from /lib/libgobject-2.0.so.0
#93 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#94 g_signal_emit
from /lib/libgobject-2.0.so.0
#95 ??
from /usr/lib/libgtk-x11-2.0.so.0
#96 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#97 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#98 ??
from /usr/lib/libgdk-x11-2.0.so.0
#99 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#100 ??
from /lib/libglib-2.0.so.0
#101 g_main_loop_run
from /lib/libglib-2.0.so.0
#102 bonobo_main
from /usr/lib/libbonobo-2.so.0
#103 main
#0 __kernel_vsyscall



----------- .xsession-errors (37 sec old) ---------------------
(evolution:2961): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2961): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa4d8018'
(evolution:2961): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa4d8138'
(evolution:2961): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
(evolution:2961): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
(evolution:2961): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
(evolution:2961): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
--------------------------------------------------

Comment 1 Susana 2007-08-10 18:49:29 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 438529 ***