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 449510 - crash in Tasks: changing encrytion optio...
crash in Tasks: changing encrytion optio...
Status: RESOLVED DUPLICATE of bug 447797
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-20 15:56 UTC by kcarter
Modified: 2007-06-20 20:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kcarter 2007-06-20 15:56:59 UTC 
Version: 2.10

What were you doing when the application crashed?
changing encrytion option


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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 163991552 vsize: 163991552 resident: 72409088 share: 40357888 rss: 72409088 rss_rlim: 4294967295
CPU usage: start_time: 1182353398 rtime: 2085 utime: 1894 stime: 191 cutime:2 cstime: 5 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 -1208961312 (LWP 3488)]
[New Thread -1259590768 (LWP 3858)]
[New Thread -1348945008 (LWP 3746)]
[New Thread -1228207216 (LWP 3651)]
[New Thread -1327965296 (LWP 3586)]
(no debugging symbols found)
0x003a4402 in __kernel_vsyscall ()

+ Trace 142450

Thread 1 (Thread -1208961312 (LWP 3488))

  • #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 ---------------------
(evolution:3488): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:3488): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:3488): camel-WARNING **: Cannot load summary file: `/home/kcarter/.evolution/mail/imap/kcarter@mx.morsco.com/folders/Trash/summary-meta': Resource temporarily unavailable
(evolution:3488): 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:3488): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa11a128'
(evolution:3488): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa11a248'
(evolution:3488): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
--------------------------------------------------
Comment 1 André Klapper 2007-06-20 18:47:59 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces



could be a dup of bug 430817
Comment 2 Karsten Bräckelmann 2007-06-20 20:35:58 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 ***