Bug 490108 – crash in Tasks: Using address book with ...

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 490108 - crash in Tasks: Using address book with ...


Summary:	crash in Tasks: Using address book with ...


Status:	RESOLVED DUPLICATE of bug 440388

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-25 11:40 UTC by JSpanier
Modified:	2007-12-04 14:21 UTC

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

Description JSpanier 2007-10-25 11:40:41 UTC

Version: 2.10

What were you doing when the application crashed?
Using address book with message composing window


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 126226432 vsize: 126226432 resident: 51384320 share: 24592384 rss: 51384320 rss_rlim: 4294967295
CPU usage: start_time: 1193308299 rtime: 2508 utime: 2245 stime: 263 cutime:49 cstime: 15 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 -1208596768 (LWP 5413)]
[New Thread -1223689328 (LWP 5715)]
[New Thread -1234179184 (LWP 5429)]
[New Thread -1244669040 (LWP 5427)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 172743

Thread 1 (Thread -1208596768 (LWP 5413))

#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/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_object_unref
from /lib/libgobject-2.0.so.0
#14 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#15 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#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 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#34 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#35 bonobo_ui_engine_prune_widget_info
from /usr/lib/libbonoboui-2.so.0
#36 ??
from /usr/lib/libbonoboui-2.so.0
#37 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#38 g_closure_invoke
from /lib/libgobject-2.0.so.0
#39 ??
from /lib/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#41 g_signal_emit
from /lib/libgobject-2.0.so.0
#42 ??
from /usr/lib/libbonoboui-2.so.0
#43 ??
from /usr/lib/libbonoboui-2.so.0
#44 ??
from /usr/lib/libbonoboui-2.so.0
#45 bonobo_ui_xml_rm
from /usr/lib/libbonoboui-2.so.0
#46 bonobo_ui_engine_xml_rm
from /usr/lib/libbonoboui-2.so.0
#47 bonobo_ui_engine_deregister_component
from /usr/lib/libbonoboui-2.so.0
#48 ??
from /usr/lib/libbonoboui-2.so.0
#49 _ORBIT_skel_small_Bonobo_UIContainer_deregisterComponent
from /usr/lib/libbonobo-2.so.0
#50 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#51 Bonobo_UIContainer_deregisterComponent
from /usr/lib/libbonobo-2.so.0
#52 bonobo_ui_component_unset_container
from /usr/lib/libbonoboui-2.so.0
#53 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#54 ??
from /usr/lib/libgtk-x11-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_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#63 ??
from /lib/libgobject-2.0.so.0
#64 g_closure_invoke
from /lib/libgobject-2.0.so.0
#65 ??
from /lib/libgobject-2.0.so.0
#66 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#67 g_signal_emit
from /lib/libgobject-2.0.so.0
#68 ??
from /usr/lib/libgtk-x11-2.0.so.0
#69 ??
from /usr/lib/libgtk-x11-2.0.so.0
#70 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#71 ??
from /lib/libgobject-2.0.so.0
#72 g_closure_invoke
from /lib/libgobject-2.0.so.0
#73 ??
from /lib/libgobject-2.0.so.0
#74 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#75 g_signal_emit
from /lib/libgobject-2.0.so.0
#76 gtk_widget_grab_focus
from /usr/lib/libgtk-x11-2.0.so.0
#77 ??
from /usr/lib/libgtkhtml-3.14.so.19
#78 ??
from /usr/lib/libgtk-x11-2.0.so.0
#79 ??
from /lib/libgobject-2.0.so.0
#80 g_closure_invoke
from /lib/libgobject-2.0.so.0
#81 ??
from /lib/libgobject-2.0.so.0
#82 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#83 g_signal_emit
from /lib/libgobject-2.0.so.0
#84 ??
from /usr/lib/libgtk-x11-2.0.so.0
#85 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#86 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#87 ??
from /usr/lib/libgdk-x11-2.0.so.0
#88 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#89 ??
from /lib/libglib-2.0.so.0
#90 g_main_loop_run
from /lib/libglib-2.0.so.0
#91 bonobo_main
from /usr/lib/libbonobo-2.so.0
#92 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  Resource id:  0x4d
(evolution:5413): libebook-WARNING **: invalid escape, passing it through
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x14056ff
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
--------------------------------------------------

Comment 1 Akhil Laddha 2007-11-20 06:45:03 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided
by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces

Comment 2 Tobias Mueller 2007-12-04 14:21:18 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 440388 ***