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 497716 - crash in Tasks: reading my mail with Evo...
crash in Tasks: reading my mail with Evo...
Status: RESOLVED DUPLICATE of bug 464159
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-17 18:43 UTC by rajsavong
Modified: 2007-11-18 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rajsavong 2007-11-17 18:43:35 UTC
What were you doing when the application crashed?
reading my mail with Evolution


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:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 144453632 vsize: 144453632 resident: 27209728 share: 15331328 rss: 27209728 rss_rlim: 4294967295
CPU usage: start_time: 1195324030 rtime: 2405 utime: 1839 stime: 566 cutime:93 cstime: 87 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 -1208621344 (LWP 3422)]
[New Thread -1245684848 (LWP 3568)]
[New Thread -1234125936 (LWP 3450)]
(no debugging symbols found)
0x0033b402 in __kernel_vsyscall ()

Thread 1 (Thread -1208621344 (LWP 3422))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #11 ??
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/libpango-1.0.so.0
  • #13 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_widget_unparent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #33 ??
    from /lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #35 ??
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #38 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #41 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #45 ??
    from /lib/libgobject-2.0.so.0
  • #46 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #47 ??
    from /lib/libgobject-2.0.so.0
  • #48 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #49 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #53 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #60 ??
    from /lib/libgobject-2.0.so.0
  • #61 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #62 ??
    from /lib/libgobject-2.0.so.0
  • #63 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #64 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #65 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #66 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #67 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #68 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #69 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #70 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #71 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #72 ??
    from /lib/libgobject-2.0.so.0
  • #73 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #74 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #75 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #76 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #77 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #78 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #79 ??
    from /lib/libgobject-2.0.so.0
  • #80 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #81 ??
    from /lib/libgobject-2.0.so.0
  • #82 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #83 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #84 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #85 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #86 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #87 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #88 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #89 ??
    from /lib/libglib-2.0.so.0
  • #90 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #91 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #92 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (70 sec old) ---------------------
(evolution:3422): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8ead018'
(evolution:3422): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8ead138'
(evolution:3422): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3422): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de groupe « Passwords-Mail »
(evolution:3422): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
Loading "installonlyn" plugin
(evolution:3422): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3422): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8ead258'
(evolution:3422): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8ead378'
--------------------------------------------------
Comment 1 Susana 2007-11-18 16:47:41 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 464159 ***