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 513874 - crash in Tasks: Closing the application,...
crash in Tasks: Closing the application,...
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-02 12:22 UTC by hans
Modified: 2008-02-02 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description hans 2008-02-02 12:22:10 UTC 
Version: 2.10

What were you doing when the application crashed?
Closing the application, after having sent an email.
Possibly the email was not sent by that time.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.24 #1 SMP PREEMPT Fri Feb 1 12:12:28 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 215650304 vsize: 215650304 resident: 74752000 share: 61960192 rss: 74752000 rss_rlim: 4294967295
CPU usage: start_time: 1201950811 rtime: 1075 utime: 984 stime: 91 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 -1208953120 (LWP 16312)]
[New Thread -1306481776 (LWP 16456)]
[New Thread -1315964016 (LWP 16376)]
[New Thread -1289766000 (LWP 16363)]
(no debugging symbols found)
0xb7f3e410 in __kernel_vsyscall ()

+ Trace 187830

Thread 2 (Thread -1306481776 (LWP 16456))

  • #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 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 PR_Lock
    from /usr/lib/libnspr4.so
  • #8 ??
    from /usr/lib/libnspr4.so
  • #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 (138 sec old) ---------------------
(evolution:13557): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:13557): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:13557): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:13557): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:13557): camel-WARNING **: camel_exception_get_id called with NULL parameter.
CalDAV Eplugin starting up ...
** (evolution:16312): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:16312): DEBUG: mailto URL program: evolution
BBDB spinning up...
(evolution:16312): e-data-server-DEBUG: Loading categories from "/home/hans/.evolution/categories.xml"
(evolution:16312): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------
Comment 1 Tobias Mueller 2008-02-02 13:27:10 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 445309 ***