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 507250 - crash in Calendar: post
crash in Calendar: post
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-04 12:32 UTC by wp-01
Modified: 2008-01-24 12:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description wp-01 2008-01-04 12:32:48 UTC
What were you doing when the application crashed?
post


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve-Gnome
Icon Theme: Clearlooks

Memory status: size: 688422912 vsize: 688422912 resident: 45322240 share: 24518656 rss: 45322240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199449691 rtime: 549 utime: 490 stime: 59 cutime:1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496410208 (LWP 3784)]
[New Thread 1126189392 (LWP 3961)]
[New Thread 1178638672 (LWP 3955)]
[New Thread 1084496208 (LWP 3845)]
[New Thread 1105209680 (LWP 3843)]
[New Thread 1084229968 (LWP 3807)]
(no debugging symbols found)
0x0000003ad180d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496410208 (LWP 3784))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 pango_attr_list_unref
    from /usr/lib64/libpango-1.0.so.0
  • #8 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #20 ??
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #33 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #34 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #35 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #36 ??
    from /lib64/libgobject-2.0.so.0
  • #37 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #38 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #39 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #40 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #41 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #42 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #43 ??
    from /lib64/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #46 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #47 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #48 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #49 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #50 ??
    from /lib64/libglib-2.0.so.0
  • #51 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #52 ??
    from /lib64/libglib-2.0.so.0
  • #53 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #54 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #55 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (22 sec old) ---------------------
** (evolution:3784): WARNING **: aspell error: No word lists can be found for the language "zh_CN".
(evolution:3784): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3784): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:3784): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x876c40'
(evolution:3784): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x876e40'
(evolution:3784): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3784): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3784): e-data-server-ui-WARNING **: 键文件没有键“smtp:__screen321;auth_PLAIN@smtp.163.com_”
(evolution:3784): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Akhil Laddha 2008-01-24 12:11:46 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 ***