Bug 460380 – crash in Tasks: clic sobre la opción nue...

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 460380 - crash in Tasks: clic sobre la opción nue...


Summary:	crash in Tasks: clic sobre la opción nue...


Status:	RESOLVED DUPLICATE of bug 438276

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-07-25 21:15 UTC by cvelazquez
Modified:	2007-07-29 18:18 UTC

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

Description cvelazquez 2007-07-25 21:15:10 UTC

Version: 2.10

What were you doing when the application crashed?
clic sobre la opción nuevo de la barra de herramientas


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-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 171458560 vsize: 171458560 resident: 70049792 share: 48738304 rss: 70049792 rss_rlim: 4294967295
CPU usage: start_time: 1185394279 rtime: 3389 utime: 3185 stime: 204 cutime:30 cstime: 9 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 -1208899872 (LWP 4633)]
[New Thread -1285153904 (LWP 4692)]
[New Thread -1246913648 (LWP 4690)]
[New Thread -1236423792 (LWP 4669)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 150551

Thread 1 (Thread -1208899872 (LWP 4633))

#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_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove
from /lib/libglib-2.0.so.0
#11 bonobo_ui_engine_update
from /usr/lib/libbonoboui-2.so.0
#12 bonobo_ui_engine_xml_merge_tree
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 _ORBIT_skel_small_Bonobo_UIContainer_setNode
from /usr/lib/libbonobo-2.so.0
#15 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#16 Bonobo_UIContainer_setNode
from /usr/lib/libbonobo-2.so.0
#17 ??
from /usr/lib/libbonoboui-2.so.0
#18 bonobo_ui_component_set
from /usr/lib/libbonoboui-2.so.0
#19 bonobo_ui_util_set_ui
from /usr/lib/libbonoboui-2.so.0
#20 e_menu_activate
from /usr/lib/evolution/2.10/libeutil.so.0
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 e_msg_composer_new_with_type
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#23 e_msg_composer_new
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#24 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#25 em_utils_compose_new_message
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#26 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#27 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#28 ??
from /usr/lib/evolution/2.10/libeshell.so.0
#29 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#35 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#40 g_signal_emit
from /lib/libgobject-2.0.so.0
#41 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /lib/libgobject-2.0.so.0
#45 g_closure_invoke
from /lib/libgobject-2.0.so.0
#46 ??
from /lib/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#48 g_signal_emit
from /lib/libgobject-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#51 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib/libgdk-x11-2.0.so.0
#53 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#54 ??
from /lib/libglib-2.0.so.0
#55 g_main_loop_run
from /lib/libglib-2.0.so.0
#56 bonobo_main
from /usr/lib/libbonobo-2.so.0
#57 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Susana 2007-07-29 18:18:16 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 438276 ***