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 498864 - crash in Tasks: clicked on send/receive!
crash in Tasks: clicked on send/receive!
Status: RESOLVED DUPLICATE of bug 440422
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-21 23:08 UTC by jonb
Modified: 2007-11-23 04:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jonb 2007-11-21 23:08:54 UTC
Version: 2.10

What were you doing when the application crashed?
clicked on send/receive!


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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 135454720 vsize: 135454720 resident: 53870592 share: 38395904 rss: 53870592 rss_rlim: 4294967295
CPU usage: start_time: 1195686468 rtime: 657 utime: 587 stime: 70 cutime:49 cstime: 24 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 -1208522000 (LWP 1064)]
[New Thread -1250571376 (LWP 1151)]
[New Thread -1230099568 (LWP 1129)]
[New Thread -1292235888 (LWP 1124)]
[New Thread -1302725744 (LWP 1123)]
[New Thread -1219200112 (LWP 1081)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208522000 (LWP 1064))

  • #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/libgtkhtml-3.14.so.19
  • #11 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #12 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #13 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #14 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #15 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #16 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #17 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #18 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #19 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #20 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #21 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #22 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #23 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #24 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #25 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #26 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #27 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #28 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #29 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #30 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #31 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #32 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #33 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #34 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #35 ??
    from /usr/lib/libgtkhtml-3.14.so.19
  • #36 html_object_destroy
    from /usr/lib/libgtkhtml-3.14.so.19
  • #37 html_engine_parse
    from /usr/lib/libgtkhtml-3.14.so.19
  • #38 gtk_html_begin_full
    from /usr/lib/libgtkhtml-3.14.so.19
  • #39 gtk_html_begin
    from /usr/lib/libgtkhtml-3.14.so.19
  • #40 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #41 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #42 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #43 ??
    from /lib/libglib-2.0.so.0
  • #44 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #45 ??
    from /lib/libglib-2.0.so.0
  • #46 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #47 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #48 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (50 sec old) ---------------------
(evolution:1064): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__gillianb%40netflare.co.uk;auth_PLAIN@mail.netflare.co.uk_'
(evolution:1064): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__gillianb%40netflare.co.uk;auth_PLAIN@mail.netflare.co.uk_' in group 'Passwords-Mail'
(evolution:1064): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__gillianb%40netflare.co.uk;auth_PLAIN@mail.netflare.co.uk_'
(evolution:1064): 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:1064): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa1b0260'
(evolution:1064): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa1b0380'
(evolution:1064): e-data-server-ui-WARNING **: Key file does not have key 'pop:__gillianb%40netflare.co.uk@pop.emailsrvr.com_'
(evolution:1064): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__gillianb%40netflare.co.uk;auth_PLAIN@smtp.emailsrvr.com_'
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-23 04:42:53 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 440422 ***