Download it now!
Bug 125977 - LibreOffice Calc won't print document if cells have specific number format
Summary: LibreOffice Calc won't print document if cells have specific number format
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-18 05:35 UTC by bugzilla
Modified: 2020-05-21 03:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (11.21 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-06-18 05:36 UTC, bugzilla
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla 2019-06-18 05:35:29 UTC
Description:
When I try to print example document I get blank page. It doesn't matter on which printer, for testing purposes I used virtual PDF printer, but error persist on real printers as well.

When I change cells format for rows from 4 to 8(Format - Cells - Number) from "Standard" to "0,00" document prints correctly.

When I change cells format for rows from 4 to 8(Format - Cells - Number) from "0,00" to "# ##0,00", for example, document stops printing.

PRINTING, FORMATTING

Steps to Reproduce:
1.Open example file
2.Try to print it

Actual Results:
Blank page for PDF printer, printer error for Kyocera.

Expected Results:
Document should print.


Reproducible: Always


User Profile Reset: No



Additional Info:
Works correctly on LO 5.2.5.1.
Also doesn't work on LO 6.0.6.2 and LO 6.1.6.3.

OS tested: Debian Jessie AMD64 and Debian Testing AMD64.
Comment 1 bugzilla 2019-06-18 05:36:24 UTC
Created attachment 152261 [details]
Example file
Comment 2 Mike Kaganski 2019-06-18 06:14:52 UTC
No repro with Version: 6.2.4.2 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded.

Note that in cells with numbers in rows 4-6 the cell formats are very strange, set to be literal text same as values in the cells (like `"10 293,14"` in cell F6). Not an issue per se, but something to mention here just in case.
Comment 3 Xisco Faulí 2019-06-18 12:46:00 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 4 bugzilla 2019-06-19 08:04:42 UTC
Tested example document with:

Version: 6.2.4.2
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU threads: 2; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded

Issue still exists on LO 6.2.4.2.
Comment 5 Xisco Faulí 2019-10-22 14:32:36 UTC
To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 6 QA Administrators 2020-04-20 03:39:17 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2020-05-21 03:42:51 UTC
Dear bugzilla,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp