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 509228 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 489872
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-13 22:13 UTC by joe_hickey
Modified: 2008-01-19 00:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description joe_hickey 2008-01-13 22:13:33 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 113655808 vsize: 113655808 resident: 32247808 share: 19992576 rss: 32247808 rss_rlim: 4294967295
CPU usage: start_time: 1200243824 rtime: 1511 utime: 1389 stime: 122 cutime:1 cstime: 5 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 -1209006368 (LWP 5517)]
[New Thread -1314231408 (LWP 5684)]
[New Thread -1272005744 (LWP 5546)]
[New Thread -1230185584 (LWP 5537)]
(no debugging symbols found)
0x00ce0402 in __kernel_vsyscall ()

+ Trace 185205

Thread 1 (Thread -1209006368 (LWP 5517))

  • #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 ??
    from /usr/lib/libpango-1.0.so.0
  • #10 g_slist_foreach
    from /lib/libglib-2.0.so.0
  • #11 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/libpango-1.0.so.0
  • #13 ??
    from /usr/lib/libpango-1.0.so.0
  • #14 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_container_forall
    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_forall
    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 gtk_widget_unparent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #41 ??
    from /lib/libgobject-2.0.so.0
  • #42 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #46 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #49 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #56 ??
    from /lib/libgobject-2.0.so.0
  • #57 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #58 ??
    from /lib/libgobject-2.0.so.0
  • #59 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #60 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #61 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #64 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #65 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #66 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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 /lib/libglib-2.0.so.0
  • #71 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #72 ??
    from /lib/libglib-2.0.so.0
  • #73 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #74 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #75 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (42 sec old) ---------------------
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5517): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Susana 2008-01-19 00:25:08 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 489872 ***