When loading the sample document from bug#87119, I get an assertion failure:
Assertion `n < std::numeric_limits<long>::max() / nMapNum' failed
from vcl/source/outdev/map.cxx:385. Debugging shows that n==0 and nMapNum==-1. The root cause seems to be that nAvailable gets the value -1 at sc/source/ui/view/output2.cxx:1722 because aAreaParam.maAlignRect.GetWidth()==3 and nTotalMargin==4.
Tor Lillqvist committed a patch related to this issue.
It has been pushed to "master":
fdo#87155: Avoid negative scaling (and assertion failures further on)
It will be available in 4.5.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
@Tor - is this fixed now?
Setting to NEW at least since you know what you're doing and reported it.
Well, it fixed the problem for me. I don't know if it was the "right" fix, though.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Is this bug fixed?
If so, could you please close it as RESOLVED FIXED?