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 464650 - crash in Tasks: I was sending an email. ...
crash in Tasks: I was sending an email. ...
Status: RESOLVED DUPLICATE of bug 426227
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-08 10:00 UTC by mehdi.bahri
Modified: 2007-08-10 19:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mehdi.bahri 2007-08-08 10:00:45 UTC
Version: 2.10

What were you doing when the application crashed?
I was sending an email.

By the way, there's another bug : when you write a mail using another account than the defaut one that uses a different SMTP server, when you synchronise, it shows the defaut account's SMTP server, not the one of the account used for sending the mail, but the server used is the right one.


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 165289984 vsize: 165289984 resident: 63475712 share: 41644032 rss: 63475712 rss_rlim: 4294967295
CPU usage: start_time: 1186564477 rtime: 2226 utime: 2049 stime: 177 cutime:225 cstime: 21 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 -1209002272 (LWP 3384)]
[New Thread -1318900848 (LWP 4325)]
[New Thread -1297921136 (LWP 3636)]
[New Thread -1291756656 (LWP 3440)]
[New Thread -1224025200 (LWP 3418)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209002272 (LWP 3384))

  • #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_free1
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libpango-1.0.so.0
  • #10 g_slist_foreach
    from /lib/libglib-2.0.so.0
  • #11 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/libpango-1.0.so.0
  • #13 ??
    from /usr/lib/libpango-1.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_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_widget_unparent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #50 ??
    from /lib/libgobject-2.0.so.0
  • #51 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #52 ??
    from /lib/libgobject-2.0.so.0
  • #53 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #54 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #55 gtk_container_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #58 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #64 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #65 ??
    from /lib/libgobject-2.0.so.0
  • #66 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #67 ??
    from /lib/libgobject-2.0.so.0
  • #68 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #69 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #70 ??
    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_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #74 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #75 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #76 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #77 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #78 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #79 ??
    from /lib/libglib-2.0.so.0
  • #80 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #81 ??
    from /lib/libglib-2.0.so.0
  • #82 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #83 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #84 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (81 sec old) ---------------------
(evolution:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a30488'
(evolution:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a305a8'
(evolution:3384): 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:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a30908'
(evolution:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a30a28'
(evolution:3384): 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:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a30c68'
(evolution:3384): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a30d88'
--------------------------------------------------
Comment 1 Susana 2007-08-10 19:21:50 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 426227 ***