Bug 482036 – crash in Tasks: Closing the Program

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 482036 - crash in Tasks: Closing the Program


Summary:	crash in Tasks: Closing the Program


Status:	RESOLVED DUPLICATE of bug 465528

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:	2007-10-01 01:19 UTC by jyuille5
Modified:	2007-10-01 15:41 UTC

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

Description jyuille5 2007-10-01 01:19:51 UTC

Version: 2.10

What were you doing when the application crashed?
Closing the Program		


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ThinIce
Icon Theme: Clearlooks

Memory status: size: 183840768 vsize: 183840768 resident: 66969600 share: 55242752 rss: 66969600 rss_rlim: 4294967295
CPU usage: start_time: 1191201224 rtime: 897 utime: 837 stime: 60 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 -1208908064 (LWP 3114)]
[New Thread -1343321200 (LWP 3200)]
[New Thread -1322341488 (LWP 3199)]
[New Thread -1266390128 (LWP 3177)]
[New Thread -1255507056 (LWP 3139)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166734

Thread 5 (Thread -1255507056 (LWP 3139))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (66 sec old) ---------------------
localuser:jeffrey being added to access control list
SESSION_MANAGER=local/jeffrey.jeffsdomain.net:/tmp/.ICE-unix/2860
CalDAV Eplugin starting up ...
** (evolution:3114): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3114): 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:3114): 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:3114): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9bdd018'
(evolution:3114): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9bdd138'
--------------------------------------------------

Comment 1 Suman Manjunath 2007-10-01 15:41:08 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 465528 ***