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 462552 - crash in Tasks: getting emails
crash in Tasks: getting emails
Status: RESOLVED DUPLICATE of bug 431396
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-01 17:58 UTC by hemsleys
Modified: 2007-09-04 23:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description hemsleys 2007-08-01 17:58:01 UTC
Version: 2.10

What were you doing when the application crashed?
getting emails		


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-33.fc7 #1 SMP Mon Jul 23 17:33:07 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: 135168000 vsize: 135168000 resident: 51642368 share: 34533376 rss: 51642368 rss_rlim: 4294967295
CPU usage: start_time: 1185906290 rtime: 2431 utime: 2247 stime: 184 cutime:2 cstime: 6 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 -1208247568 (LWP 3891)]
[New Thread -1359430768 (LWP 16477)]
[New Thread -1348940912 (LWP 16476)]
[New Thread -1306981488 (LWP 16472)]
[New Thread -1252684912 (LWP 15931)]
[New Thread -1264399472 (LWP 3920)]
[New Thread -1220801648 (LWP 3914)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208247568 (LWP 3891))

  • #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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #21 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 bonobo_ui_engine_prune_widget_info
    from /usr/lib/libbonoboui-2.so.0
  • #24 ??
    from /usr/lib/libbonoboui-2.so.0
  • #25 g_cclosure_marshal_VOID__POINTER
    from /lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libbonoboui-2.so.0
  • #31 ??
    from /usr/lib/libbonoboui-2.so.0
  • #32 bonobo_ui_xml_rm
    from /usr/lib/libbonoboui-2.so.0
  • #33 bonobo_ui_engine_xml_rm
    from /usr/lib/libbonoboui-2.so.0
  • #34 ??
    from /usr/lib/libbonoboui-2.so.0
  • #35 _ORBIT_skel_small_Bonobo_UIContainer_removeNode
    from /usr/lib/libbonobo-2.so.0
  • #36 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #37 Bonobo_UIContainer_removeNode
    from /usr/lib/libbonobo-2.so.0
  • #38 ??
    from /usr/lib/libbonoboui-2.so.0
  • #39 bonobo_ui_component_rm
    from /usr/lib/libbonoboui-2.so.0
  • #40 gal_view_menus_unmerge
    from /usr/lib/evolution/2.10/libmenus.so.0
  • #41 ??
    from /usr/lib/evolution/2.10/libmenus.so.0
  • #42 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #44 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #45 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #46 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #47 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #48 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #49 ??
    from /lib/libglib-2.0.so.0
  • #50 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #51 ??
    from /lib/libglib-2.0.so.0
  • #52 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #53 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #54 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (14 sec old) ---------------------
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
warning: .dynamic section for "/usr/lib/libcups.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-04 23:21:15 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 431396 ***