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 447212 - crash in Tasks: Sorting sent items by fr...
crash in Tasks: Sorting sent items by fr...
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
Depends on:
Blocks:
 
 
Reported: 2007-06-13 16:40 UTC by nick.southwell
Modified: 2007-06-14 11:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description nick.southwell 2007-06-13 16:40:20 UTC
What were you doing when the application crashed?
Sorting sent items by from


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 224559104 vsize: 224559104 resident: 111280128 share: 48590848 rss: 111280128 rss_rlim: 4294967295
CPU usage: start_time: 1181726966 rtime: 10150 utime: 9283 stime: 867 cutime:1 cstime: 7 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 -1208629536 (LWP 3769)]
[New Thread -1300247664 (LWP 4122)]
[New Thread -1311130736 (LWP 3837)]
[New Thread -1271927920 (LWP 3813)]
[New Thread -1249326192 (LWP 3811)]
(no debugging symbols found)
0x00668402 in __kernel_vsyscall ()

Thread 1 (Thread -1208629536 (LWP 3769))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
  • #6 camel_message_info_ptr
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #9 e_tree_model_value_at
    from /usr/lib/evolution/2.10/libetable.so.0
  • #10 e_table_sorting_utils_tree_sort
    from /usr/lib/evolution/2.10/libetable.so.0
  • #11 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #12 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    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/evolution/2.10/libetable.so.0
  • #19 ethi_change_sort_state
    from /usr/lib/evolution/2.10/libetable.so.0
  • #20 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #21 gnome_canvas_marshal_BOOLEAN__BOXED
    from /usr/lib/libgnomecanvas-2.so.0
  • #22 ??
    from /lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/evolution/2.10/libemiscwidgets.so.0
  • #28 ??
    from /usr/lib/evolution/2.10/libemiscwidgets.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /lib/libgobject-2.0.so.0
  • #31 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #39 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #40 ??
    from /lib/libglib-2.0.so.0
  • #41 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #42 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #43 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (567 sec old) ---------------------
Increasing itip formatter search count to 9
Decreasing itip formatter search count toWindow manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x620005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x620005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x62000df (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x62000df (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6204317 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6204317 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x62000df (Losses___n)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 André Klapper 2007-06-14 11:39:20 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 ***