Bug 111430

Summary:	Cannot print from LO on Samsung M2835dw most of the time (printer flashes red blinking light: no paper) - printing works from printer (test page) or other applications
Product:	LibreOffice	Reporter:	e.lodewijks
Component:	Printing and PDF export	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	serval2412
Priority:	medium
Version:	5.1.6.2 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description e.lodewijks 2017-08-07 07:53:43 UTC

Description:
When I try to print from LO (mostly Writer), a print job is sent to the printer. The print dialogue disappears shortly after (it also disappears from the task bar). The printer makes a short sound, but then immediately stops and flashes the red light. I sometimes see in the 'Printers' config screen that it says 'Out of Paper', while there is lots of paper present.

This only happens for documents with text. Empty pages seem to print just fine.

The files are stored on a NFS share on the network.

Other applications (Firefox (printing of emails), texteditor (Pluma)) print just fine.

Holding a button on the printer for some seconds prints the test page just fine.

This problem has started some weeks ago - I am sorry, I don't know when exactly and if it was after a certain update.

Printer config hasn't changed. Also in LO, documents and printer settings have not changed. It is A4 and the default tray.

Steps to Reproduce:
1. Open a non-empty page in Writer or Calc.
2. Print.

Actual Results:
A click is heard from the printer, after which the printer immediately stops and flashes a red light.

Expected Results:
Print the document.

Reproducible: Sometimes

User Profile Reset: Yes, I reset the profile, but didn't fix the problem.
I have the same problem, though less frequently it seems, on the other computer in the office.

Additional Info:
Ubuntu Mate 16.04.2
Linux 4.10.0-28-generic

LO Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
CPU Threads: 2; OS Version: Linux 4.10; UI Render: default;
Locale: en-ZA (en_ZA.UTF-8)

Printer: Samsung M2835dw
Printer connected via: dnssd://Samsung%20M283x%20Series%20(SEC30CDA7F3427B)._printer._tcp.local/

The files are stored on an NFS drive on the network. I edit them and then try to print them.

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Comment 1 Julien Nabet 2017-08-07 08:06:40 UTC

5.1.X and 5.2.X versions are EOL.
Could you give a try to a recent LO version? (last stable one is 5.3.4)
I think you find it on LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)

Comment 2 Julien Nabet 2017-08-07 08:07:04 UTC

s/you find it/you may find it/

Comment 3 e.lodewijks 2017-09-08 10:03:15 UTC

I installed the indicated fresh LO installation.

Printing seems fine now.

However, I could not open any of the locked documents at all.

I had to go on the other computer with the 'original' version of LO, undo the locking of the file and save the file (on the NFS share).

After that, I could open the file on the new LO (after having commented out two lines in /usr/bin/soffice) and it works just fine now.

I suppose that locking/ accessibility of the files might have somehow been an issue.

This bug report can be closed as the issue is no longer current for me and I can no longer test it.

As a final comment from my side:
It seems to me that the combination of marking files as 'Read Only', NFS, and different versions of LO seem to makes files pretty much inaccessible.

Comment 4 e.lodewijks 2017-09-08 10:04:18 UTC

(In reply to e.lodewijks from comment #3)
> I installed the indicated fresh LO installation.
> 
> Printing seems fine now.
> 
> However, I could not open any of the locked documents at all.
> 
> I had to go on the other computer with the 'original' version of LO, undo
> the locking of the file and save the file (on the NFS share).
> 
> After that, I could open the file on the new LO (after having commented out
> two lines in /usr/bin/soffice) and it works just fine now.
> 
> I suppose that locking/ accessibility of the files might have somehow been
> an issue.
> 
> This bug report can be closed as the issue is no longer current for me and I
> can no longer test it.
> 
> As a final comment from my side:
> It seems to me that the combination of marking files as 'Read Only', NFS,
> and different versions of LO seem to makes files pretty much inaccessible.



s/any of the locked files/any of the 'Read Only' files/