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 511582 - crash in Tasks: File -> Exit -> Crash
crash in Tasks: File -> Exit -> Crash
Status: RESOLVED DUPLICATE of bug 503155
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-23 17:25 UTC by Melissa A. VandenBrink
Modified: 2008-02-24 12:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Melissa A. VandenBrink 2008-01-23 17:25:41 UTC
Version: 2.10

What were you doing when the application crashed?
File -> Exit -> Crash


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.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v0.3
Icon Theme: OSX_Cursors_v0.2

Memory status: size: 152051712 vsize: 152051712 resident: 58785792 share: 37691392 rss: 58785792 rss_rlim: 4294967295
CPU usage: start_time: 1201100980 rtime: 3677 utime: 3425 stime: 252 cutime:2 cstime: 6 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 -1208756512 (LWP 19447)]
[New Thread -1210856560 (LWP 12503)]
[New Thread -1302889584 (LWP 19531)]
[New Thread -1246262384 (LWP 19482)]
[New Thread -1221346416 (LWP 19481)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1210856560 (LWP 12503))

  • #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 camel_message_info_ptr
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #9 camel_folder_summary_save
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #11 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #12 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 camel_store_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6


----------- .xsession-errors (417280 sec old) ---------------------
JACK tmpdir identified as [/dev/shm]
play stio: Can't open input file `/usr/share/gnome/sounds/email.wav': No such file or directory
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
play stio: Can't open input file `/usr/share/gnome/sounds/email.wav': No such file or directory
JACK tmpdir identified as [/dev/shm]
** (evolution:4198): WARNING **: bbdb: Failed to add new contact: EBookStatus returned 8
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2008-02-24 12:23:13 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 503155 ***