Forum Bugs

Software Error: pack error: packed nothing.

mrose
i am preparing a file that, regrettably, must load several large .jpg files. this is 6.0 rev 5 on a macbook pro. my guess is that this is a memory allocation error of some kind. i'd really like a way of generating the entire job in one file...

thanks!

/mtr

% prince --verbose 2009.html
prince: loading XML input: 2009.html
prince: loading style sheet: calendar.css
prince: loading image: 2009/images/Cover.jpg
prince: loading image: 2009/images/Akathist 1-2.jpg
prince: loading image: 2009/images/Akathist 3-4.jpg
prince: loading image: 2009/images/Akathist 5-6.jpg
prince: loading image: 2009/images/Akathist 7-8.jpg
prince: loading image: 2009/images/Akathist 9-10.jpg
prince: loading image: 2009/images/Akathist 11-12.jpg
prince: loading image: 2009/images/Akathist 13-14.jpg
prince: loading image: 2009/images/Akathist 15-16.jpg
prince: loading image: 2009/images/Akathist 17-18.jpg
prince: loading image: 2009/images/Akathist 19-20.jpg
prince: loading image: 2009/images/Akathist 21-22.jpg
prince: loading image: 2009/images/Akathist 23-24.jpg
prince: used font: Hoefler Text, Italic
prince: used font: Hoefler Text, Regular
prince: used font: Optima, Regular
prince: used font: Optima, ExtraBlack
Uncaught Mercury exception:
Software Error: pack error: packed nothing.
mikeday
Nasty! Are you able to email me the document, or if it's too big to email, perhaps send me a link to download it? That would help us to diagnose the problem.
mrose
let me check for permission to send you the images.

i think i found the problem though: pilot error. i had some parts that look like this

<div class='jan'> ... </div>

and other places like this

<div id='jan'> ... </div>

and i had swapped div.jan { ... } with #jan { ... } in the css, so a width was being assigned to the wrong <div/>s. when fixed the css, it compiled just fine...

anyway, let me check on the image permissions...
mikeday
Perhaps replace the images with blank images of the same size? That might still trigger the bug. Prince really shouldn't be giving error messages like that, regardless of what the document is like.