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 445994 - crash in Calendar: Input password of my ema...
crash in Calendar: Input password of my ema...
Status: RESOLVED DUPLICATE of bug 426807
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 457010 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-10 10:36 UTC by chjflx
Modified: 2007-07-29 13:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description chjflx 2007-06-10 10:36:42 UTC
What were you doing when the application crashed?
Input password of my email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 138010624 vsize: 138010624 resident: 47783936 share: 34410496 rss: 47783936 rss_rlim: 4294967295
CPU usage: start_time: 1181471449 rtime: 422 utime: 382 stime: 40 cutime:87 cstime: 7 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 -1208318240 (LWP 2971)]
[New Thread -1283597424 (LWP 3069)]
[New Thread -1294087280 (LWP 3066)]
[New Thread -1221055600 (LWP 2993)]
(no debugging symbols found)
0x00d14402 in __kernel_vsyscall ()

Thread 1 (Thread -1208318240 (LWP 2971))

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


----------- .xsession-errors (32 sec old) ---------------------
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:2971): 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?)
BBDB spinning up...
(evolution:2971): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94b4020'
(evolution:2971): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94b4140'
error getting update info:  Cannot open/read repomd.xml file for repository: updates
(evolution:2971): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:2971): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2971): e-data-server-ui-WARNING **: 键文件没有组“Passwords-Mail”
(evolution:2971): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 palfrey 2007-06-29 16:35:23 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

*** This bug has been marked as a duplicate of 426807 ***
Comment 2 André Klapper 2007-07-29 13:52:53 UTC
*** Bug 457010 has been marked as a duplicate of this bug. ***