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 516747 - crash in Tasks: Reteving email
crash in Tasks: Reteving email
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-15 21:31 UTC by lsgerrit
Modified: 2008-02-18 09:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lsgerrit 2008-02-15 21:31:42 UTC
Version: 2.10

What were you doing when the application crashed?
Reteving email


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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 170242048 vsize: 170242048 resident: 69304320 share: 52957184 rss: 69304320 rss_rlim: 4294967295
CPU usage: start_time: 1203110137 rtime: 2209 utime: 2050 stime: 159 cutime:69 cstime: 20 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 -1208543520 (LWP 2823)]
[New Thread -1230779504 (LWP 3370)]
[New Thread -1283761264 (LWP 3363)]
[New Thread -1260266608 (LWP 3252)]
[New Thread -1241269360 (LWP 2829)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208543520 (LWP 2823))

  • #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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #12 gtk_rc_style_unref
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #17 gtk_rc_style_unref
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 g_datalist_clear
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-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 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #24 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #25 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #33 ??
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #39 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 gtk_container_foreach
    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 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #59 ??
    from /lib/libgobject-2.0.so.0
  • #60 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #61 ??
    from /lib/libgobject-2.0.so.0
  • #62 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #63 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #64 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #66 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #67 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #68 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #69 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #70 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #71 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #72 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #73 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #74 ??
    from /lib/libgobject-2.0.so.0
  • #75 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #76 ??
    from /lib/libgobject-2.0.so.0
  • #77 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #78 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #79 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #80 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #81 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #82 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #83 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #84 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #85 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #86 ??
    from /lib/libglib-2.0.so.0
  • #87 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #88 ??
    from /lib/libglib-2.0.so.0
  • #89 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #90 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #91 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (55 sec old) ---------------------
(evolution:2823): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa80f380'
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2a0322d
(evolution:2823): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution:2823): 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:2823): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa80f4a0'
(evolution:2823): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa80f5c0'
QClipboard::setData: Cannot set X11 selection owner for PRIMARY
QClipboard::setData: Cannot set X11 selection owner for PRIMARY
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-18 09:16:40 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 447591 ***