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 493806 - crash in Tasks: Changed a POP account to...
crash in Tasks: Changed a POP account to...
Status: RESOLVED DUPLICATE of bug 449652
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-05 17:47 UTC by steveb05
Modified: 2007-11-06 16:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description steveb05 2007-11-05 17:47:12 UTC
Version: 2.10

What were you doing when the application crashed?
Changed a POP account to IMAP (gmail) and resynced all folders


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 193990656 vsize: 193990656 resident: 72650752 share: 55816192 rss: 72650752 rss_rlim: 4294967295
CPU usage: start_time: 1194284645 rtime: 715 utime: 663 stime: 52 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208793376 (LWP 3593)]
[New Thread -1275073648 (LWP 3793)]
[New Thread -1359918192 (LWP 3778)]
[New Thread -1402119280 (LWP 3648)]
[New Thread -1285563504 (LWP 3619)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208793376 (LWP 3593))

  • #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 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
(evolution:3593): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:3593): 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:3593): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed
(evolution:3593): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9bf6240'
(evolution:3593): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed
(evolution:3593): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9bf6360'
(evolution:3593): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:3593): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------
Comment 1 André Klapper 2007-11-06 16:51:05 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 449652 ***