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 482105 - crash in Tasks: marking 4 emails as read
crash in Tasks: marking 4 emails as read
Status: RESOLVED DUPLICATE of bug 475330
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-01 09:28 UTC by barry.reilly
Modified: 2007-10-23 17:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description barry.reilly 2007-10-01 09:28:16 UTC
Version: 2.10

What were you doing when the application crashed?
marking 4 emails as read


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:59:51 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: 627937280 vsize: 627937280 resident: 56328192 share: 36433920 rss: 56328192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191229117 rtime: 1087 utime: 1015 stime: 72 cutime:1098 cstime: 82 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 46912496398480 (LWP 23669)]
[New Thread 1084229968 (LWP 23743)]
[New Thread 1147435344 (LWP 23699)]
[New Thread 1094719824 (LWP 23688)]
(no debugging symbols found)
0x0000003ec120d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496398480 (LWP 23669))

  • #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_layout_line_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libpango-1.0.so.0
  • #9 ??
    from /usr/lib64/libpango-1.0.so.0
  • #10 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 gtk_widget_unparent
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #25 ??
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib64/evolution/2.10/libeutil.so.0
  • #31 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #32 ??
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #35 gtk_menu_shell_activate_item
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #39 ??
    from /lib64/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #42 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #43 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #44 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #45 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #46 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #47 ??
    from /lib64/libglib-2.0.so.0
  • #48 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #49 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #50 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (1116 sec old) ---------------------
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
BBDB spinning up...
(evolution:23669): e-data-server-DEBUG: Loading categories from "/home/breilly/.evolution/categories.xml"
(evolution:23669): e-data-server-DEBUG: Loaded 29 categories
(evolution:23669): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed
(evolution:23669): libebook-CRITICAL **: file e-book.c: line 3807: assertion `source && E_IS_SOURCE (source)' failed
(evolution:23669): 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:23669): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x876ca0'
(evolution:23669): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8768a0'
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-23 17:02:23 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 475330 ***