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 455362 - crash in Tasks: selecting several messag...
crash in Tasks: selecting several messag...
Status: RESOLVED DUPLICATE of bug 450041
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-09 23:54 UTC by etolkacheva
Modified: 2007-08-01 13:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description etolkacheva 2007-07-09 23:54:03 UTC
Version: 2.10

What were you doing when the application crashed?
selecting several messages in the INBOX for deleting


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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 639672320 vsize: 639672320 resident: 65142784 share: 40603648 rss: 65142784 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184007778 rtime: 1100 utime: 1004 stime: 96 cutime:0 cstime: 1 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 46912496361056 (LWP 3004)]
[New Thread 1115699536 (LWP 4154)]
[New Thread 1115965776 (LWP 3033)]
[New Thread 1084229968 (LWP 3027)]
(no debugging symbols found)
0x000000321a40d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496361056 (LWP 3004))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 pango_attr_list_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #9 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #10 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #12 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #15 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #17 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #18 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #19 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #20 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #22 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #23 ??
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #31 ??
    from /lib64/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #35 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #36 g_value_unset
    from /lib64/libgobject-2.0.so.0
  • #37 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #38 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #39 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #40 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #41 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #42 ??
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #43 html_engine_parse
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #44 gtk_html_begin_full
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #45 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #46 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #47 ??
    from /lib64/libglib-2.0.so.0
  • #48 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #49 ??
    from /lib64/libglib-2.0.so.0
  • #50 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #51 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #52 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
(evolution:3004): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3004): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x886c40'
(evolution:3004): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x886e40'
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------
Comment 1 palfrey 2007-08-01 13:16: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 450041 ***