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 489640 - crash in Tasks: closing the application ...
crash in Tasks: closing the application ...
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-24 01:27 UTC by Mike Edwards
Modified: 2007-10-24 07:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Mike Edwards 2007-10-24 01:27:14 UTC 
Version: 2.10

What were you doing when the application crashed?
closing the application window using the "x" icon


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 176095232 vsize: 176095232 resident: 95657984 share: 33550336 rss: 95657984 rss_rlim: 4294967295
CPU usage: start_time: 1193141639 rtime: 1450 utime: 1331 stime: 119 cutime:233 cstime: 48 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 -1208342816 (LWP 16032)]
[New Thread -1368032368 (LWP 19702)]
[New Thread -1315312752 (LWP 16060)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172406

Thread 2 (Thread -1368032368 (LWP 19702))

  • #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 (31 sec old) ---------------------
(evolution:16032): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:16032): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed
(evolution:16032): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream'
(evolution:16032): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:16032): camel-CRITICAL **: camel_stream_printf: assertion `CAMEL_IS_STREAM (stream)' failed
(evolution:16032): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream'
(evolution:16032): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:16032): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-24 07:28:59 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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