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 456306 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431342
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 458321 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-12 17:04 UTC by ahr
Modified: 2007-08-17 13:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ahr 2007-07-12 17:04:26 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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 677908480 vsize: 677908480 resident: 46723072 share: 16482304 rss: 46723072 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184259858 rtime: 107 utime: 97 stime: 10 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 46912496389728 (LWP 22202)]
[New Thread 1115699536 (LWP 22223)]
[New Thread 1147169104 (LWP 22222)]
[New Thread 1168148816 (LWP 22215)]
[New Thread 1136679248 (LWP 22211)]
[New Thread 1105209680 (LWP 22208)]
[New Thread 1084229968 (LWP 22205)]
(no debugging symbols found)
0x000000387720d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496389728 (LWP 22202))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 camel_message_info_ptr
    from /usr/lib64/libcamel-provider-1.2.so.10
  • #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 (166814 sec old) ---------------------
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:12691): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
** (swriter.bin:15697): WARNING **: Error getting printer list: HTTP Error in POST Success
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-08-01 13:22:38 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 431342 ***
Comment 2 palfrey 2007-08-17 13:10:23 UTC
*** Bug 458321 has been marked as a duplicate of this bug. ***