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 480056 - crash in Tasks: Sending an email with 3 ...
crash in Tasks: Sending an email with 3 ...
Status: RESOLVED DUPLICATE of bug 449652
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-25 02:57 UTC by klanger
Modified: 2007-11-06 16:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description klanger 2007-09-25 02:57:34 UTC
Version: 2.10

What were you doing when the application crashed?
Sending an email with 3 attachments.


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.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: 176451584 vsize: 176451584 resident: 71802880 share: 46661632 rss: 71802880 rss_rlim: 4294967295
CPU usage: start_time: 1190644377 rtime: 2816 utime: 2631 stime: 185 cutime:0 cstime: 2 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 -1208232224 (LWP 5060)]
[New Thread -1327154288 (LWP 5492)]
[New Thread -1358378096 (LWP 5491)]
[New Thread -1379357808 (LWP 5479)]
[New Thread -1347888240 (LWP 5140)]
[New Thread -1247900784 (LWP 5136)]
[New Thread -1273070704 (LWP 5122)]
(no debugging symbols found)
0x006e8402 in __kernel_vsyscall ()

Thread 1 (Thread -1208232224 (LWP 5060))

  • #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 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (274 sec old) ---------------------
(evolution:5060): 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:5060): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa1347e0'
(evolution:5060): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa134900'
(evolution:5060): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x380690e (Me at 25 W); these messages lack timestamps and therefore suck.
--- Hash table keys for warning below:
--> file:///home/klanger
(nautilus:5335): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(eog:5433): GdkPixbuf-CRITICAL **: _gdk_pixbuf_load_module_unlocked: assertion `image_module->module == NULL' failed
--------------------------------------------------
Comment 1 André Klapper 2007-11-06 16:51:01 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 449652 ***