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 448699 - crash in Tasks: resetting send server in...
crash in Tasks: resetting send server in...
Status: RESOLVED DUPLICATE of bug 447797
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-18 07:24 UTC by joan-bob
Modified: 2007-06-18 20:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description joan-bob 2007-06-18 07:24:50 UTC 
What were you doing when the application crashed?
resetting send server in evolution preferences after finding it was set incorrectly.


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: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: 135557120 vsize: 135557120 resident: 35561472 share: 21110784 rss: 35561472 rss_rlim: 4294967295
CPU usage: start_time: 1182151167 rtime: 686 utime: 632 stime: 54 cutime:0 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 -1208916256 (LWP 5707)]
[New Thread -1262511216 (LWP 5749)]
[New Thread -1260246128 (LWP 5743)]
[New Thread -1230099568 (LWP 5728)]
(no debugging symbols found)
0x00402402 in __kernel_vsyscall ()

+ Trace 141814

Thread 1 (Thread -1208916256 (LWP 5707))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_str_hash
    from /lib/libglib-2.0.so.0
  • #6 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #7 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (13 sec old) ---------------------
** (evolution:5707): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:5707): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5707): e-data-server-DEBUG: Loading categories from "/home/fc007/.evolution/categories.xml"
(evolution:5707): e-data-server-DEBUG: Loaded 22 categories
(evolution:5707): 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:5707): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ac140'
(evolution:5707): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ac260'
(evolution:5707): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-06-18 20:49:53 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 447797 ***