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 496427 - crash in Tasks: trying to read a very la...
crash in Tasks: trying to read a very la...
Status: RESOLVED DUPLICATE of bug 239441
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-13 12:47 UTC by dave
Modified: 2007-11-18 13:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dave 2007-11-13 12:47:55 UTC 
Version: 2.10

What were you doing when the application crashed?
trying to read a very large nightly system report.


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-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 219025408 vsize: 219025408 resident: 124719104 share: 31576064 rss: 124719104 rss_rlim: 4294967295
CPU usage: start_time: 1194956771 rtime: 19337 utime: 18450 stime: 887 cutime:124 cstime: 201 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 -1208317200 (LWP 15442)]
[New Thread -1269847152 (LWP 15839)]
[New Thread -1234887792 (LWP 15838)]
[New Thread -1284506736 (LWP 15471)]
[New Thread -1221375088 (LWP 15460)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 177406

Thread 1 (Thread -1208317200 (LWP 15442))

  • #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 /usr/lib/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #7 resort_model
    from /usr/lib/evolution/2.10/libetable.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (9 sec old) ---------------------
** (evolution:2830): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2830): 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
CalDAV Eplugin starting up ...
** (evolution:15442): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:15442): 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:15442): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:15442): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel'
(evolution:15442): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed
--------------------------------------------------
Comment 1 Susana 2007-11-18 13:24:16 UTC 
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 239441 ***