Bug 86127 - Loading and printing documents makes LibO unresponsive for long periods of time (HP & Brother printers)
Summary: Loading and printing documents makes LibO unresponsive for long periods of ti...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-10 19:45 UTC by msutton1973
Modified: 2016-10-10 11:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description msutton1973 2014-11-10 19:45:00 UTC
Opening files and printing files will make LO unresponsive.

If I go to:

   Options --> Load/Save --> General
   disable "Load printer settings with the document"

Then documents load fine but as soon as I print it will become unresponsive for atleast 30 seconds. The printers are networked printers and work fine with other programs.

This is on a Windows 7sp1 x64 computer.
Comment 1 Julien Nabet 2014-11-10 19:58:15 UTC
Could you give a try to last stable LO version 4.3.3?
Also, for the test, rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows)
Indeed, there won't be any official update for 4.2 branch after 4.2.7 LO version. (see https://wiki.documentfoundation.org/ReleasePlan)

Finally, could you give brand and model of your printer?
Comment 2 msutton1973 2014-11-10 20:14:13 UTC
(In reply to Julien Nabet from comment #1)
> Could you give a try to last stable LO version 4.3.3?
> Also, for the test, rename your LO directory profile (see
> https://wiki.documentfoundation.org/UserProfile#Windows)
> Indeed, there won't be any official update for 4.2 branch after 4.2.7 LO
> version. (see https://wiki.documentfoundation.org/ReleasePlan)
> 
> Finally, could you give brand and model of your printer?

I originally started with 4.3.3 had this happening so installed 4.2.7 and renamed the profile directory, still had the problem. There is 2 shared printers one is a "HP Laserjet 3030" the other is a "Brother MFC-9320CW".

This is at a local public Library we have 8 public computers running linux with libreoffice and they all work fine, so it has to be a windows thing.
Comment 3 Julien Nabet 2014-11-10 21:20:03 UTC
Thank you for your feedback, I put it back to UNCONFIRMED since I've got no more questions for the moment.
Comment 4 msutton1973 2014-11-10 22:10:19 UTC
One other thing ... the windows computers kept showing offline when they weren't so I had to install this hotfix: http://support.microsoft.com/kb/2713128 I don't know if that might cause the problem.
Comment 5 tommy27 2015-09-30 05:06:42 UTC
4.2.7 and 4.3.3 are obsolete LibO releases.

please retest with current LibO 4.4.5 or 5.0.2 and tell if the issue is still present.

status -> NEEDINFO
Comment 6 Xisco Faulí 2016-09-11 19:54:37 UTC Comment hidden (obsolete)
Comment 7 Xisco Faulí 2016-10-10 11:13:19 UTC
Dear Bug Submitter,

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-20161010