Hello, I've been maintaining an ODT document for many years (so this could be some legacy trash being dragged in the meta-code)...But recently the export-to-pdf button up top has crashed Writer.
***I have reverted the attached document back to 126.96.36.199, but it should happen when the document is opened in the newer release.
Steps to reproduce:
1. ....Open the attached file in LibO 188.8.131.52
2. ....Click the Export to PDF button on th etoolbar
It should crash when the progress meter is near 20-30%. It may be image related, and it usually hesitates at each image point in the document.
Operating System: Mac OS X
Version: 184.108.40.206 release
Last worked in: 220.127.116.11 release
Attachment is too large, so we may have to figure out a Plan B.
can you try and reduce the document size through deleting pages until the bug still occurs with minimal content? This would help to reduce the attachment size and make it easier to try and find the reason for crashing.
Otherwise you could try and send the document to my email or upload it to a file hoster and send the link.
Thank you for your help.
Created attachment 83547 [details]
Target image in my document that crashes the PDF Export
(In reply to comment #2)
> can you try and reduce the document size through deleting pages until the
> bug still occurs with minimal content? This would help to reduce the
> attachment size and make it easier to try and find the reason for crashing.
> Otherwise you could try and send the document to my email or upload it to a
> file hoster and send the link.
> Thank you for your help.
Done. I started to do that, but then I kept paring it down out of curiosity to get it as lean as possible.
This image (attached) has been in my document for over 2 years and spanned many, many versions past.
I can confirm with 18.104.22.168 and 22.214.171.124 on OSX 10.8.4. pdf export works with 126.96.36.199. It also works with 188.8.131.52 on Ubuntu linux.
Looks similar to https://bugs.freedesktop.org/show_bug.cgi?id=67416 but not sure if it really has the same cause, so setting status to new.
Thanks for reporting.
I swapped out the jpg with a differently-sourced version, and all is
well. So I'd say that it implies corrupt jpg content (either metadata or
visual). LibreOffice appears to function well, though it would be nice
to have it scan for valid jpg content and warn, if that was the issue.
On 8/2/2013 5:03 PM, email@example.com wrote:
> Michael <mailto:firstname.lastname@example.org> changed bug 67677
> What Removed Added
> Status UNCONFIRMED NEW
> Severity normal major
> Priority medium high
> Version 184.108.40.206 release 220.127.116.11 rc
> Ever confirmed 1
> *Comment # 5 <https://bugs.freedesktop.org/show_bug.cgi?id=67677#c5>
> on bug 67677 <https://bugs.freedesktop.org/show_bug.cgi?id=67677> from
> Michael <mailto:email@example.com> *
> I can confirm with 18.104.22.168 and 22.214.171.124 on OSX 10.8.4. pdf export works with
> 126.96.36.199. It also works with 188.8.131.52 on Ubuntu linux.
> Looks similar tohttps://bugs.freedesktop.org/show_bug.cgi?id=67416 <show_bug.cgi?id=67416> but not
> sure if it really has the same cause, so setting status to new.
> Thanks for reporting.
> You are receiving this mail because:
> * You reported the bug.
Same root cause as bug #67416, fixed by commit a321be22907c47e2e378c494f0de9f3f68af5167 .
*** This bug has been marked as a duplicate of bug 67416 ***