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 463185 - crash in Tasks: changing mail settings
crash in Tasks: changing mail settings
Status: RESOLVED DUPLICATE of bug 451816
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-03 16:22 UTC by madhusudan
Modified: 2007-08-04 09:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description madhusudan 2007-08-03 16:22:49 UTC
Version: 2.10

What were you doing when the application crashed?
changing mail settings	


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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 149667840 vsize: 149667840 resident: 48820224 share: 35627008 rss: 48820224 rss_rlim: 4294967295
CPU usage: start_time: 1186157146 rtime: 393 utime: 367 stime: 26 cutime:1 cstime: 4 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 -1208518944 (LWP 5066)]
[New Thread -1263465584 (LWP 5164)]
[New Thread -1273955440 (LWP 5123)]
[New Thread -1246798960 (LWP 5095)]
[New Thread -1236309104 (LWP 5093)]
(no debugging symbols found)
0x009ad402 in __kernel_vsyscall ()

Thread 1 (Thread -1208518944 (LWP 5066))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 e_account_set_string
    from /usr/lib/libedataserver-1.2.so.9
  • #6 exchange_config_listener_authenticate
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #7 exchange_operations_get_exchange_account
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #8 org_gnome_exchange_commit
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
  • #9 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #10 e_plugin_invoke
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #11 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #12 e_config_commit
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #13 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #14 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #19 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #23 ??
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #26 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 gtk_button_released
    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 ??
    from /lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #39 ??
    from /lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #42 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #46 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #47 ??
    from /lib/libglib-2.0.so.0
  • #48 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #49 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #50 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (175 sec old) ---------------------
(process:3706): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function
(process:3706): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Adobe FlashPlayer: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0);
(process:3787): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function
(process:3787): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Adobe FlashPlayer: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0);
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:5143): WARNING **: Unexpected kerberos error -1765328230
** (evolution:5143): WARNING **: Unexpected kerberos error -1765328230
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-04 09:50:30 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 451816 ***