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 205216 - evolution-mail crashes on send/recieve
evolution-mail crashes on send/recieve
Status: RESOLVED DUPLICATE of bug 205095
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Normal blocker
: ---
Assigned To: Not Zed
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-07-23 15:43 UTC by fran
Modified: 2001-08-10 01:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description fran 2001-07-23 14:46:06 UTC 
Package: Evolution
Priority: Blocker
Version: Gnome Evolution 0.11.99

Synopsis: evolution-mail crashes on send/recieve
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
configure evolution (from cvs) with:

./autogen.sh --enable-file-locking=no --enable-dot-locking=yes

when evolution is run, it loads fine, however when trying to collect mail from a pop-3 mail account, it tries to lock the mbox and
then eventually crashes.

Output from evolution-mail:

camel-lock.c(99): trying to lock '/home/spectre/evolution/local/debian gnu-hurd//mbox.lock', attempt 0
camel-lock.c(127): tmp lock created, link count is 1
There is an existing lock -37934 seconds old
camel-lock.c(99): trying to lock '/home/spectre/evolution/local/debian gnu-hurd//mbox.lock', attempt 1
camel-lock.c(127): tmp lock created, link count is 1
There is an existing lock -37932 seconds old
camel-lock.c(99): trying to lock '/home/spectre/evolution/local/debian gnu-hurd//mbox.lock', attempt 2
camel-lock.c(127): tmp lock created, link count is 1
There is an existing lock -37930 seconds old
camel-lock.c(99): trying to lock '/home/spectre/evolution/local/debian gnu-hurd//mbox.lock', attempt 3
camel-lock.c(127): tmp lock created, link count is 1
There is an existing lock -37928 seconds old
camel-lock.c(99): trying to lock '/home/spectre/evolution/local/debian gnu-hurd//mbox.lock', attempt 4
camel-lock.c(127): tmp lock created, link count is 1
There is an existing lock -37926 seconds old
camel-lock.c(149): failed to get lock after 5 retries
camel-local-provider-ERROR **: file camel-mbox-folder.c: line 148 (mbox_lock): assertion failed: (mf->lockfd == -1)
aborting...
[Switching to Thread 5271]
Program received signal SIGABRT, Aborted.

Output from a backtrace on evolution-mail (after it had aborted):

(gdb) bt

+ Trace 7468

  • #0 kill
    from /lib/libc.so.6
  • #1 pthread_kill
    from /lib/libpthread.so.0
  • #2 raise
    from /lib/libpthread.so.0
  • #3 abort
    from /lib/libc.so.6
  • #4 g_logv
    from /usr/lib/libglib-1.2.so.0
  • #5 g_log
    from /usr/lib/libglib-1.2.so.0
  • #6 mbox_lock
    at camel-mbox-folder.c line 148
  • #7 camel_local_folder_lock
    at camel-local-folder.c line 242
  • #8 mbox_append_message
    at camel-mbox-folder.c line 184
  • #9 camel_folder_append_message
    at camel-folder.c line 492
  • #10 do_move
    at camel-filter-driver.c line 418
  • #11 e_sexp_term_eval
    at e-sexp.c line 643
  • #12 term_eval_begin
    at e-sexp.c line 587
  • #13 e_sexp_term_eval
    at e-sexp.c line 633
  • #14 e_sexp_eval
    at e-sexp.c line 1215
  • #15 camel_filter_driver_filter_message
    at camel-filter-driver.c line 893
  • #16 camel_filter_driver_filter_folder
    at camel-filter-driver.c line 779
  • #17 filter_folder_filter
    at mail-ops.c line 113
  • #18 fetch_mail_fetch
    at mail-ops.c line 276
  • #19 mail_msg_received
    at mail-mt.c line 336
  • #20 thread_received_msg
    at e-msgport.c line 467
  • #21 thread_dispatch
    at e-msgport.c line 538
  • #22 pthread_start_thread
    from /lib/libpthread.so.0 



Unknown reporter: fran@thinkgeek.co.uk, changed to bugbuddy-import@ximian.com.
Comment 1 Luis Villa 2001-07-25 02:10:03 UTC 
notzed: in channel, it was noted that the reason this occurs is
because of the space in the file name. Remove the space in the file
name and the crash stops happening.
Comment 2 Not Zed 2001-07-25 16:23:15 UTC 
Hmm, the negative 'lock old' is the problem, its found a lock created
about a day in advance, and wont remove it.

STill the space doesn't make sense, unless stat is being funny.
Comment 3 Not Zed 2001-08-10 01:45:03 UTC 
Does this still crash?

Or just fail to lock? (like it should)
Comment 4 Not Zed 2001-08-10 01:48:11 UTC 

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