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 493073 - crash in Tasks: I had just finished adju...
crash in Tasks: I had just finished adju...
Status: RESOLVED DUPLICATE of bug 407187
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-03 15:25 UTC by mlavalle
Modified: 2007-11-20 06:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mlavalle 2007-11-03 15:25:50 UTC
Version: 2.10

What were you doing when the application crashed?
I had just finished adjusting some account settings in Evolution.  The only thing I changed was adding a GPG Key ID.  I did notice that there were two IMAP Header tabs, and I clicked on both.  Both were the same.


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.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Tango

Memory status: size: 209891328 vsize: 209891328 resident: 62488576 share: 47312896 rss: 62488576 rss_rlim: 4294967295
CPU usage: start_time: 1194101793 rtime: 945 utime: 891 stime: 54 cutime:1 cstime: 3 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 -1208457504 (LWP 4745)]
[New Thread -1292313712 (LWP 4800)]
[New Thread -1260192880 (LWP 4799)]
[New Thread -1270686832 (LWP 4763)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208457504 (LWP 4745))

  • #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:4745): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x948a140'
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
** (process:4972): WARNING **: can't lock memory: Cannot allocate memory
WARNING: not using secure memory for passwords
** Message: init gpgme version 1.1.4
(seahorse:4972): Gtk-WARNING **: Error loading icon: Failed to open file '/usr/share/pixmaps/seahorse//22x22/seahorse-person.png': No such file or directory
(evolution:4745): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-20 06:49: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 407187 ***