Bug 131240 - LibreOffice hangs when it tries to print, cannot set PostScript
Summary: LibreOffice hangs when it tries to print, cannot set PostScript
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-09 16:26 UTC by Alex
Modified: 2020-09-29 17:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
cups 'error_log' during print test (1.06 MB, text/plain)
2020-03-09 16:29 UTC, Alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2020-03-09 16:26:17 UTC
Description:
SYSTEM
Linux 5.5.8-arch1-1 x86_64 GNU/Linux
LibreOffice: Version:6.4.1.2; Build:5.4.1.3; VCL:gtk3
gtk3: 1:3.24.14, a2ps 4.14-8, etc.
 (not aware of any missing dependencies; in general, Arch software updated daily)

Printer: HP LaserJet Pro M201-M202 PCL6; USB connected.
CUPS: 2.3.1
Window Manager: fluxbox:1.3.7-5 
Firefox: 73.0.1 (64-bit) for Arch Linux

System prints perfectly from
- Command line
- GUI Firefox, xterm

PROBLEM
When trying to print [File>Print...] from "Writer Document",
 LO hangs (solid) at a "Print preview" screen.
Whether on
 Printer Setup>Properties>Device>Printer language type:
  Automatic:PDF or PostScript (Level from driver) or PSL 1, 2 or 3

Isolated at:
System boot > CUPS boot (with new 'error_log' file >
 LO up (in xterm: /bin/libreoffice > create new Witer Document (one ASCII char for test) > Print

Steps to Reproduce:
1.System boot > CUPS boot (with new 'error_log' file >
 LO up (in xterm: /bin/libreoffice > create new Witer Document (one ASCII char for test) > Print
2.
3.

Actual Results:
LO frozen solid

Expected Results:
File sent to printer.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
LibreOffice: Version:6.4.1.2; Build:5.4.1.3; VCL:gtk3
Comment 1 Alex 2020-03-09 16:29:17 UTC
Created attachment 158521 [details]
cups 'error_log' during print test
Comment 2 Timur 2020-03-31 08:00:38 UTC
Please explain Steps to Reproduce, what's System boot > CUPS boot.
Do you experience only with physical printer or also with Print to PDF?
Comment 3 Xisco Faulí 2020-03-31 11:47:00 UTC
OTOH, do you reproduce it with any document or with a specific one ?
Comment 4 Alex 2020-04-01 03:29:24 UTC
(In reply to Timur from comment #2)
> Please explain Steps to Reproduce, what's System boot > CUPS boot.
Shorthand for
 1. Power-on the machine
 2. The Arch system comes up including CUPS
 3. Log on
 4. Start fluxbox and go to graphics mode
 5. Start LibreOffice
 6. Test printing
 7. Kill LibreOffice 
 8. Examine the 'error_log'

Sorry for the confusion.

> Do you experience only with physical printer or also with Print to PDF?
Only with the physical printer.
I do not know how to Print to PDF.  I can export to PDF.
However, GOOD QUESTION.  I should mention when I go to
 Printer Setup>Properties>Device>Printer language type
no matter what choice I originally make, like PostScript ...1,2,3, etc.
it turns out the only choice LO leaves in the end (after I re-check) is just
Automatic:PDF.

(In reply to Xisco Faulí from comment #3)
> OTOH, do you reproduce it with any document or with a specific one ?
I've tried with Writer Documents and Calc Spreadsheets.
Comment 5 Timur 2020-04-01 05:14:37 UTC
(In reply to Alex from comment #4)
> I do not know how to Print to PDF. 
Install cups-printer package and you will have PDF as a printer. 
When print in that, PDF will be in PDF folder in your 'home'.
Comment 6 QA Administrators 2020-09-29 04:06:53 UTC Comment hidden (obsolete)
Comment 7 Alex 2020-09-29 16:37:53 UTC
The bug if fixed.
Has disappeared somewhere, sometime between version 6.4.1.2 and current 7.1.0.2
(I hadn't kept exact, close track).
Kudos and many thanks to the people responsible.
As a separate comment:  would've been nice to have had an announcement on
131240 about the fix attempt.  At the very least, it would've prevented the extra
level of anxiety for the QA Administrators I'm detecting in Comment 6,
especially during these unprecedented times.

Best Wishes,
-- Alex