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 444258 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 443865
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-05 08:23 UTC by sylvain
Modified: 2007-06-10 17:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sylvain 2007-06-05 08:23:54 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: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: 690778112 vsize: 690778112 resident: 103710720 share: 18006016 rss: 103710720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181031815 rtime: 1225 utime: 1196 stime: 29 cutime:0 cstime: 0 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 46912496377440 (LWP 10921)]
[New Thread 1094719824 (LWP 10962)]
[New Thread 1178638672 (LWP 10954)]
[New Thread 1168148816 (LWP 10953)]
[New Thread 1105209680 (LWP 10942)]
(no debugging symbols found)
0x00000030fda0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496377440 (LWP 10921))

  • #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 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (37260 sec old) ---------------------
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:15241): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-06-10 17:01:21 UTC

*** This bug has been marked as a duplicate of 443865 ***