Bug 73610 - save print area remembered just for first sheet
Summary: save print area remembered just for first sheet
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-01-14 15:25 UTC by matteo.cappello
Modified: 2016-05-09 20:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description matteo.cappello 2014-01-14 15:25:44 UTC
saves print area only for the firs sheet, doesn't save it for the other ones
Comment 1 tommy27 2014-01-14 20:12:54 UTC
please give us a clearer description... post a screenshot, an example...
if you have troubles with english speak italian and I'll translate in the tracker for you.
Comment 2 matteo.cappello 2014-01-20 08:37:06 UTC
ho un file di Calc con due fogli di calcolo, ciascuno con suddivisione della finestra (menù finestra –> dividi -> fissa)
imposto le aree di stampa una per ciascuno dei due fogli del file;
imposto, per ciascun foglio, che ci siano righe e colonne di intestazione che si ripetono (menù formato -> aree di stampa ->modifica)
salvo e chiudo il file;
riapro il file e l’area di stampa è stata salvata per intero soltanto nel primo dei due fogli di calcolo, mentre nel secondo foglio sono state salvate soltanto le righe e le colonne da ripetere e non l’area di stampa.
Comment 3 tommy27 2014-01-20 10:37:39 UTC
try uploading a test file with the features you are talking about.
It will be easier to replicate the issue.

once I have the file I'll prepare a proper english translation.


uploada qui un file con le caratteristiche di cui parli.
sarà più facile replicare il problema.

una volta visto il file cercherò di tradurre la tua segnalazione.
Comment 4 tommy27 2014-06-22 08:30:03 UTC
please tell if issue is still reproducible in current LibO release
Comment 5 raal 2014-09-19 20:42:12 UTC
According to comment 3 and 4 setting as needinfo.
Comment 6 Owen Genat (retired) 2015-03-16 18:35:09 UTC
Seems like a duplicate of bug 55273.
Comment 7 QA Administrators 2015-10-14 19:50:46 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-10-14
Comment 8 QA Administrators 2016-05-09 20:07:37 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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

This INVALID Message was generated on: 2016-05-09