Bug 513916 – crash in Tasks: check mail

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 513916 - crash in Tasks: check mail


Summary:	crash in Tasks: check mail


Status:	RESOLVED DUPLICATE of bug 431396

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-02 17:06 UTC by peterlexp
Modified:	2008-02-04 12:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description peterlexp 2008-02-02 17:06:28 UTC

Version: 2.10

What were you doing when the application crashed?
check mail


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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 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: 135868416 vsize: 135868416 resident: 49061888 share: 37556224 rss: 49061888 rss_rlim: 4294967295
CPU usage: start_time: 1201975335 rtime: 1476 utime: 1343 stime: 133 cutime:0 cstime: 0 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 -1208285472 (LWP 13980)]
[New Thread -1252246640 (LWP 14083)]
[New Thread -1305670768 (LWP 14082)]
[New Thread -1230857328 (LWP 13984)]
(no debugging symbols found)
0x006b9402 in __kernel_vsyscall ()

+ Trace 187852

Thread 1 (Thread -1208285472 (LWP 13980))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/evolution/2.10/libetable.so.0
#11 ??
from /usr/lib/evolution/2.10/libetable.so.0
#12 ??
from /lib/libglib-2.0.so.0
#13 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#14 ??
from /lib/libglib-2.0.so.0
#15 g_main_loop_run
from /lib/libglib-2.0.so.0
#16 bonobo_main
from /usr/lib/libbonobo-2.so.0
#17 main
#0 __kernel_vsyscall



----------- .xsession-errors (183 sec old) ---------------------
Could not lock '/var/spool/mail//dbmail'
***MEMORY-ERROR***: evolution[13753]: GSlice: assertion failed: sinfo->n_allocated > 0
CalDAV Eplugin starting up ...
** (evolution:13980): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:13980): 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:13980): 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:13980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa335018'
(evolution:13980): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa335138'
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-04 12:59:53 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 431396 ***