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 443865 - crash in Tasks: opening a folder.
crash in Tasks: opening a folder.
Status: RESOLVED DUPLICATE of bug 438756
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 443940 444258 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-04 10:07 UTC by sylvain
Modified: 2007-06-12 01:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sylvain 2007-06-04 10:07:46 UTC
What were you doing when the application crashed?
opening a folder.


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 838201344 vsize: 838201344 resident: 166305792 share: 24559616 rss: 166305792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180949289 rtime: 7456 utime: 6958 stime: 498 cutime:146 cstime: 39 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496373344 (LWP 4663)]
[New Thread 1094719824 (LWP 6672)]
[New Thread 1126189392 (LWP 6645)]
[New Thread 1084229968 (LWP 4944)]
[New Thread 1136945488 (LWP 4702)]
[New Thread 1157658960 (LWP 4695)]
(no debugging symbols found)
0x00000030fda0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496373344 (LWP 4663))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #5 e_table_sorting_utils_tree_sort
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #7 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #8 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #9 ??
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #13 gnome_canvas_marshal_BOOLEAN__BOXED
    from /usr/lib64/libgnomecanvas-2.so.0
  • #14 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #15 ??
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /lib64/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
  • #19 ??
    from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
  • #20 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #22 ??
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #30 ??
    from /lib64/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #32 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #33 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2a724a0
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2a725e0
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2aaabee77f10
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2a72400
subcell_view 0x2aaab9774420 deleted before the a11y object 0x29c6800
subcell_view 0x2aaab9774420 deleted before the a11y object 0x29102a0
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2a72220
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2a722c0
subcell_view 0x2aaab9774420 deleted before the a11y object 0x2aaab988b500
(evolution:4663): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4663): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 André Klapper 2007-06-10 17:01:07 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 André Klapper 2007-06-10 17:01:16 UTC
*** Bug 443940 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-06-10 17:01:21 UTC
*** Bug 444258 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-06-12 01:00:21 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 438756 ***