https://bugs.documentfoundation.org/show_bug.cgi?id=154830
Mike Kaganski <mikekagan...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #13 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to Dennis Wage from comment #5)
> It's not just Calc either. Writer is doing the same thing.
(In reply to Dennis from comment #10)
> It is true I have a laser printer that is not turned on. However,
> LibreOffice Writer (latest version of LO) does not have a problem with this,
> nor does any other application outside of LibreOffice.
> Writer used to have a problem on earlier editions, but it was fixed.
(In reply to Dennis Wage from comment #12)
> It was an unavailable printer. But, my question is why?
Dennis: you might notice that Dennis Wage continues to have this problem with
Writer, too. No, it was not fixed, it's just you don't see this problem with
your current *documents* or *system setup*.
Dennis Wage: the "why" is because LibreOffice uses the information *reported by
printer driver* for some things; e.g., for pagination in Calc. Unfortunately,
obtaining this information is not done "in background", but rather, the program
waits until the information is returned. Whenever the printer driver needs some
time to either communicate with printer, or to discover that the printer is
unavailable, that timeout "hangs" LibreOffice.
When does this happen? When the printer *used by the current document* is
unavailable. Two options here: either the current document does not have a
specific printer configured, and then *the system default printer is used*, and
that happens to be unavailable - in this case, people would tend to see this
hang almost independently of the document; or the current document has a
specific (non-default) printer configured, which happens to be unavailable. In
this latter case, only specific documents would suffer; and in this case, the
option to not apply the printer configuration from the document would help
(unlike the former case). But the underlying problem is the same.
Yes this is a bug, I do not say that it's OK. I only explain the status quo.
*** This bug has been marked as a duplicate of bug 42673 ***
--
You are receiving this mail because:
You are the assignee for the bug.
