GNOME Bugzilla – Bug 446678
crash in Email:
Last modified: 2007-06-12 10:54:22 UTC
What were you doing when the application crashed? 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 96092160 vsize: 96092160 resident: 38825984 share: 30416896 rss: 38825984 rss_rlim: 4294967295 CPU usage: start_time: 1181645119 rtime: 58 utime: 47 stime: 11 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208908064 (LWP 6241)] (no debugging symbols found) 0x00a89402 in __kernel_vsyscall ()
+ Trace 140295
Thread 1 (Thread -1208908064 (LWP 6241))
----------- .xsession-errors --------------------- warning: /var/named/named.ip6.local saved as /var/named/named.ip6.local.rpmsave warning: /var/named/named.local saved as /var/named/named.local.rpmsave warning: /var/named/named.zero saved as /var/named/named.zero.rpmsave Writing new pickle Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 2336, in on_tvNPDevices_cursor_changed path = model.get_path(iter) TypeError: iter should be a GtkTreeIter set PageSize = A4 /usr/bin/gs: found /usr/bin/hpijs: found /usr/lib/cups/filter/foomatic-rip: found CalDAV Eplugin starting up ... (evolution:6164): e-data-server-DEBUG: Loaded default categories CalDAV Eplugin starting up ... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 425129 ***