← Back to team overview

vm team mailing list archive

[Bug 520997] Re: VM beeps and complains about extent-live-p

 

> Are you trying to display images inline in Emacs?

Yes, it seems to happen when VM tries to display an inline image.

> Did this use to work in older versions of VM? Which ones?

I never noticed it with beta 1 or 8.0.*.  I don't have any mail which
I'm positive I looked at while using beta 1, and which fails now.  So
I'm not completely sure it started in beta 2, but it certainly is the
impression I get.

> extent-live-p seems to be an Xemacs function. Your VM seems to think
you are running Xemacs. Any idea why?

vm-xemacs-p is nil and vm-fsfemacs-p is t, so it looks good that far.

I enabled debug-on-error, and get this backtrace

  extent-live-p(nil)
  vm-display-some-image-strips-on-extents(("/tmp/vm290958820" "/tmp/vm345913789" "/tmp/vm480891890" "/tmp/vm554284691" "/tmp/vm656641022" "/tmp/vm76520228" "/tmp/vm854892630" "/tmp/vm962671635" "/tmp/vm1051916178" "/tmp/vm1199569807" "/tmp/vm125172957") nil tiff "TIFF" (0))
  vm-process-filter-display-some-image-strips(#<process image strip maker for /tmp/vm111109884> "XZXX0XZXX\n")

I found these functions in vm-mime.el.  vm-process-filter-display-some-
image-strips is set as a filter both in vm-mime-display-internal-image-
xemacs-xxxx and in vm-mime-display-internal-image-fsfemacs-21-xxxx.  I
can't see any obvious conditionals on fsfemacs versus xemacs in vm-
process-filter-display-some-image-strips nor in vm-display-some-image-
strips-on-extents.  But maybe there is some not so obvious ones?

-- 
VM beeps and complains about extent-live-p
https://bugs.launchpad.net/bugs/520997
You received this bug notification because you are a member of VM
development team, which is the registrant for VM.

Status in VM (View Mail) for Emacs: New

Bug description:
I'm using emacs 21.4 on a RHEL5 system.  I installed vm 8.1.0 beta 2.  Now for some messages I get a very long beep, then a pause, and then a shorter beep.  It has only happened with messages including an image so far, so I'm guessing it is connected to image display.  But I have no evidence that is the case.

I attach a sample message where this does happen.  I've stripped it down, but left the image intact so it's still a bit big.

The *Messages* buffer show the messages below after this has happened.  The last two messages are repeated many times.

…
Loading tapestry...done
1 message, 0 new, 0 unread, 0 deleted
Decoding MIME message...
Decoding base64... done
Decoding MIME message... done
End of message 1 from SSMSC_Support@xxxxxxx
1 message, 0 new, 0 unread, 0 deleted
Checking for new mail for /users/uddeborg/vm-bug...
1 message, 0 new, 0 unread, 0 deleted
error in process filter: vm-display-some-image-strips-on-extents: Symbol's function definition is void: extent-live-p
error in process filter: Symbol's function definition is void: extent-live-p
error in process filter: vm-display-some-image-strips-on-extents: Symbol's function definition is void: extent-live-p
error in process filter: Symbol's function definition is void: extent-live-p
error in process filter: vm-display-some-image-strips-on-extents: Symbol's function definition is void: extent-live-p
error in process filter: Symbol's function definition is void: extent-live-p





References