mptopdf fails to execute 'mtx-base.lua' (bug in luatex?)

Bug #776692 reported by weissenb
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
context (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: context

For a simple Metapost file, e.g. x.mp with content:

beginfig(0)
  draw (0,0)--(1,1);
endfig;
end.

mptopdf x.mp

yields

MTXrun | forcing cache reload
MTXrun | resolvers: warning: no lua configuration files found
MTXrun | resolvers
MTXrun | resolvers
MTXrun | the resolver databases are not present or outdated
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | resolvers: remembering file 'mtx-base.lua'
MTXrun | resolvers: using suffix based filetype 'lua'
MTXrun | unknown script 'base.lua' or 'mtx-base.lua'

and fails to generate a PDF file (I believe this is just a symptom of some bug in luatex, since mpost x.mp works -- executing luatools yields the same error message).

I'm using Ubuntu 11.04, updated from 10.10 (mptopdf worked before the update).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: context 2010.07.30-1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 3 16:32:57 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: context
UpgradeStatus: Upgraded to natty on 2011-04-29 (4 days ago)

Revision history for this message
weissenb (georg-weissenbacher) wrote :
Revision history for this message
Adam Reviczky (reviczky) wrote :
Revision history for this message
Frederik Eaton (frederik-launchpad) wrote :

I'm sorry, but what is the workaround for this bug? It's not clear to me from those two links. And why would Ubuntu ship a broken context package?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in context (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.