I have LibreOffice Version: 6.0.5.2 (x64) on Windows 10 Pro ver 1803. My printer is a Funai Kodak Verite 65 plus. Since upgrading LibreOffice I can't print. I've uninstalled and reinstalled printer driver. When I send a document to the print queue the queue is empty I can print from pdf and all other applications, just not LibreOffice. Seem to remember having this problem before after a previous upgrade.
Could you upgrade to 6.0.6 + rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) ?
HI and thanks for your help. I've tried that but still doesn't print, in fact, document never appears in print queue. Any other suggestions?
Wendy: just to be sure, if you create a brand new file (eg: Writer odt), type "test" and click Print icon, do you get something like an error message? Xisco: put you in cc because it's the third bug I see about printing pb on Windows. See tdf#119179 + related to this one but closed as WFM because the user had reinstalled everything and it was ok.
Hi Did that and it printed! BUT if I copy the contents of the document I really want to print into the new document it still doesn't print. The doc I'm trying to print consists of a multi-page table. Just tried a doc that only has a few lines of simple text and that also prints. What doesn't it like about tables???
Would it be possible you attach an example file after having sanitized it (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)? It could be useful we can give it a try to reproduce this.
Created attachment 144173 [details] Forthcoming itinerary table File attached
On Win7 with LO 6.0.6, I got this: - if printer is PDFCreator, no pb, I could save the pdf. - if printer is a Ricoh (via network), the printer queue displays an error on the doc (so impossible to print it).
*** Bug 119179 has been marked as a duplicate of this bug. ***
Hi Julien, What happen if you try to print with older versions of LibreOffice? 5.0 or 4.0 ?
I've previously been able to print the document before I upgraded to LO 6.*.* If I export it as a pdf I can print it but not as a LO document.
*** Bug 117977 has been marked as a duplicate of this bug. ***
Trying to pinpoint the issue, I change the title to indicate some printer types so far: Funai Kodak Dell Ricoh ? I have Konica network printer and it works. So not simply network printer issue.
Wendy, I added Bug 115649 to See Also to see, not comment there about this bug. Since it's something specific, you should help us with different answers and tests: 1. is it true you can print new documents, problem is only for old/existing documents? 2. did you switch, one by one, Options - Load/Save - General: Load user-specific OR printer settings with the document 3. dis you try to deinstall 64-bit LO and install 32-but LO 6.0.6? 4. can you try free procdump portable tool from Sysinternals to get dump, like this: path-to\procdump.exe soffice.bin -h path-to\soffice.bin.dmp
With regards to reply: Q1. is it true you can print new documents, problem is only for old/existing documents? A1. I can print a simple writer text document, I haven't tried a multi-page table document Q2. did you switch, one by one, Options - Load/Save - General: Load user-specific OR printer settings with the document A2. tried each of these options but didn't make any difference. Q3. dis you try to deinstall 64-bit LO and install 32-but LO 6.0.6? A3. Yes, made no difference. Q4. can you try free procdump portable tool from Sysinternals to get dump, like this: path-to\procdump.exe soffice.bin -h path-to\soffice.bin.dmp A4. Sorry, but I don't understand this. I am not a power Windows user, straightforward us of applications only. Please can you explain this one a little more. Thanks
Get Sysinternals Suite from https://docs.microsoft.com/en-us/sysinternals/ Put it to some path-to-Sysinternals folder Run 32-bit LO Open Command Prompt type (replacing path) path-to-Sysinternals\procdump.exe soffice.bin -h path-to-put\soffice.bin.dmp You'll see dump and get soffice.bin.dmp file. Upload file here.
Not sure what I'm doing wrong but I followed the instructions 4 times leaving LO and the command prompt running for longer but no dump. Here's the text from the command prompt window, can you tell me what I'm doing wrong? C:\WINDOWS\system32>D:\Documents\Downloads\Sysinternals\SysinternalsSuite\procdump.exe soffice.bin -h D:\Documents\Downloads\Sysinternals\dump_path\soffice.bin.dmp ProcDump v9.0 - Sysinternals process dump utility Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards Sysinternals - www.sysinternals.com Process: soffice.bin (11740) Process image: C:\Program Files (x86)\LibreOffice\program\soffice.bin CPU threshold: n/a Performance counter: n/a Commit threshold: n/a Threshold seconds: 10 Hung window check: Enabled Log debug strings: Disabled Exception monitor: Disabled Exception filter: [Includes] * [Excludes] Terminate monitor: Disabled Cloning type: Disabled Concurrent limit: n/a Avoid outage: n/a Number of dumps: 1 Dump folder: D:\Documents\Downloads\Sysinternals\dump_path\ Dump filename/mask: soffice.bin Queue to WER: Disabled Kill after dump: Disabled Press Ctrl-C to end monitoring without terminating the process. [18:50:48] The process has exited. [18:50:48] Dump count not reached.
There's no dump, meaning no crash in LO. So I wonder why there's no print. Is it related to Bug 116370? Please test with https://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/ that now has it fixed.
Wendy, Julien, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version.
I've tried that, still the same problem. Can I "downgrade" to an earlier version of LO and if so, how?
(In reply to wendy from comment #19) > I've tried that, still the same problem. > > Can I "downgrade" to an earlier version of LO and if so, how? The master build installs separately, so you can just uninstall it ("LibreOfficeDev").
(In reply to wendy from comment #19) > I've tried that, still the same problem. > > Can I "downgrade" to an earlier version of LO and if so, how? According to the summary, it stops working with 6.0.5. Could you please confirm it works with version 6.0.4 ?
(In reply to Xisco Faulí from comment #21) > (In reply to wendy from comment #19) > > I've tried that, still the same problem. > > > > Can I "downgrade" to an earlier version of LO and if so, how? > > According to the summary, it stops working with 6.0.5. > Could you please confirm it works with version 6.0.4 ? You can download it from https://downloadarchive.documentfoundation.org/libreoffice/old/6.0.4.2/. Thanks
(In reply to wendy from comment #19) > I've tried that, still the same problem. BTW, Could you please paste the info from Help - about LibreOffice ?
@Wendy, Any update ?
Hi, no, still won't print, even "downgraded" to version 6.0.0.3 (x64). Is this the info you requested: Version: 6.0.0.3 (x64) Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-US (en_US); Calc: CL I'm going to be out of the country for three weeks wef 2 Sept
Just for information, I don't reproduce this on Win7 (64 bits) with LO 6.1.0.3 64 bits. Now I must recognize this bug resembles a bit "Schrödinger", at least in my case. I mean I noticed several jobs (certainly some made with 6.0.6) on the printer which were present on the queue. To explain a bit further, at office we got several network printers. Each time we print, the job is sent to the printer but not printed. I must go to the printer, authentify with some badge, then I can see the whole of my jobs to print. From this, I can print and remove job or remove job. In brief, I'm a bit afraid that the result of my tests may provide wrong/tainted information :-(
*** Bug 119644 has been marked as a duplicate of this bug. ***
Adding HP in title considering tdf#119644
*** Bug 119660 has been marked as a duplicate of this bug. ***
libreoffice won’t even send to the printer everything else on my laptop can print except for libreoffice. I have windows 10 and the printer is a Epson 4750 it also won’t let me print on my Epson 440. It won’t even send it to my printers print queue which it was doing before and printer fine I updated libreoffice but it was still sending to the printer and printing until about 2-3 weeks ago. It was working fine now it won’t even send to any printer at all. I do not know why I was sent to this page when it is 100% libreoffice not anything else seeing as how everywhere else on my laptop sends to every printer. I’ve tried everything and still libreoffice won’t send to any printer and everything else on my computer will.
I don't reproduce issue with Win 10 ver 1709 printing to Konica network printer. So far, only specifics we have is that issue occures in Windows 10 ver 1803, as written by Wendy and Dejoie. James and Jensen and David, can you please confirm your Windows 10 version? Did you all test with with master https://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/ ? Please do.
*** Bug 119879 has been marked as a duplicate of this bug. ***
Michael: thought it could be interesting to put this tracker in next ESC.
Thank you Julian [bug 119879], I followed your advice Bug 119250 and printed a new file (saved or not): it appears well in the printer queue.
*** Bug 119902 has been marked as a duplicate of this bug. ***
I didn't reproduce issue with Win 10 ver 1803 printing existing document (and attached one) to Konica network printer. So we may have an issue with some printers only.
*** Bug 120020 has been marked as a duplicate of this bug. ***
(In reply to Julien Nabet from comment #37) > *** Bug 120020 has been marked as a duplicate of this bug. *** From initial comment of this tdf, LO 6.1.1.2 + Canon MX 410 series printer + Windows 10 home
NO problem printing on Windows 10 Version: 6.2.0.0.alpha0+ (x64) Build ID: 3208fcb3a36d75d6290d9c548430682f153b09db CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-20_22:43:20 Locale: ro-RO (ro_RO); Calc: threaded
Upgraded to Version: 6.0.6.2 (x64) Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 8; OS: Windows 10.0; UI render: GL; Locale: en-GB (en_US); Calc: CL Still have the same problem, document doesn't even appear in the print queue.
Just looking at dups and trying to summarize, the pb is on: - only on Windows, more specifically on Win10 (so not reproduced in WinVista, Win7 or Win8 unless I missed something) - 6.0 and 6.1 branches - only for some printers (only network printers or some reproduce this with usb printers?) - seems 64 bits only (I don't know if some people use Win10 32 bits on tablets or something else). To use a brand new file "might" help in some cases but obviously, the goal is to make LO work for every file So for those who have the pb, it could be interesting to give a try to daily build 6.2 (see https://dev-builds.libreoffice.org/daily/master/) Of course, it's just for the test since it's an alpha version (so not at all a stable one).
Hello, having to switch permanently between LibreOffice and WPS because of other bugs that I will go back, I notice that: - I can not print either from WPS Writer through PDF Suite 2016, but without problems on my HP Series 5810 printer; - Impressions work from LibreOffice and WPS through Microsoft Print to PDF; - Reminder: the impression since LibreOffice through PDF Suite 2016 does not work. If it can help you. Best regards.
Michael: do you know if someone works on this one? Indeed, I saw nothing in ESC these last weeks so I wonder if this one is still on the scope of blocker bugs.
Hi Julien, we are really hoping for some bisection action here by someone affected so we can more easily find the root cause - if we have that, fixing it should become reasonably easy I hope. It was dropped from the ESC agenda due to lack of concrete details IIRC.
Hi guys I still have this problem. I would appreciate a resolution if at all possible. Thanks Wendy
(In reply to wendy from comment #45) > Hi guys > I still have this problem. I would appreciate a resolution if at all > possible. All affected can try bibisecting to find the problem: Install cygwin: https://wiki.documentfoundation.org/QA/Bibisect/Windows#Setting_up_Environment Then in your cygwin environment: git clone git://gerrit.libreoffice.org/bibisect-win32-6.0 Wait a long time while it downloads. Finally start bibisecting: https://wiki.documentfoundation.org/QA/Bibisect/Windows#Bibisecting_the_Bug I don't remember if the 6.0 repo has "latest" tag, so use "master" instead if needed.
Hi Wendy - sorry for the problem; we're struggling to identify the issue. What would really help would be if you could help bisect the issue - by working out exactly which version this issue crept into. I believe Xisco can help out training on bibisection here if you're interested - it would be great to get more data on this ! Thanks for helping out by filing, and getting involved.
I always try to use the current version so whatever version was the current stable install when I submitted the problem would have been the version I was using. I had recently updated to that version. Currently I am using: LibreOffice Writer 10/06/2018 Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: group threaded Windows specifications Edition Windows 10 Home Version 1803 Installed on 7/3/2018 OS build 17134.285 I use SUMo to identify my out of date software so that I can monitor all my apps. Previously I was using Secunia PSI which has been discontinued. I still have the original problem I reported while OpenOffice correctly prints the file. I am using a HP Officejet Pro 8600 Plus.
Unable to test the master release you referenced as that is beyond my knowledge and skill set.
(In reply to Michael Meeks from comment #47) > Hi Wendy - sorry for the problem; we're struggling to identify the issue. > What would really help would be if you could help bisect the issue - by > working out exactly which version this issue crept into. I believe Xisco can > help out training on bibisection here if you're interested - it would be > great to get more data on this ! Thanks for helping out by filing, and > getting involved. Sorry, but this sounds well outside my skills set. Explain please.
(In reply to wendy from comment #50) > (In reply to Michael Meeks from comment #47) > > Hi Wendy - sorry for the problem; we're struggling to identify the issue. > > What would really help would be if you could help bisect the issue - by > > working out exactly which version this issue crept into. I believe Xisco can > > help out training on bibisection here if you're interested - it would be > > great to get more data on this ! Thanks for helping out by filing, and > > getting involved. > > Sorry, but this sounds well outside my skills set. Explain please. Explanation is in my comment 46. Xisco is our QA engineer, who can help you (or anyone else affected by this bug) go through the steps necessary to pinpoint the issue.
*** Bug 120517 has been marked as a duplicate of this bug. ***
From Bug 120517: "All my other programs print, with one exception. I installed OpenOffice and it does not print. "
Dear LO users that have this critical issue. As written before, we must pinpoint it before it can be solved, and we were not able to reproduce. Looking around, seems that there's a general issue with printing in Win 10 1803. Can you please try the following advices - if haven't alredy: A. delete and reinstall printer with latest drivers? B. enable the SMB1.0 client in Windows Features? C. Workaround (please backup the registry first before making changes): Press windows key + R. Type 'regedit' in the Open box, and then click OK. Locate, and then click the following registry subkey if it exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade On the Edit menu, click Delete, and then click Yes to confirm the removal of the PostSPUpgrade registry key. Restart your PC (OR run ‘net stop spooler’ followed by ‘net start spooler’ from an elevated command prompt). Please note this is best effort to help. And please write your feeedback.
Please test and respond to the previous message. Or confirm that issue is solved somehow, like an upgrade to a new Windows 10 version.
I solved my printing problem. I restarted LO in Safe Mode, then sent the user configuration to archive. When I restarted in normal mode, it began printing. (Not: I had manually renamed the user config file with no result.)
I had same issue. Windows 10, version 6.0.7.3 (x64). Issue appeared when I upgraded to this version. It happened with different printers selected, including Microsoft Print to PDF. The issue did not appear if I started in Safe Mode. The issue did not appear in software other than LibreOffice. I re-booted. I started LibreOffice in safe mode. I selected Reset to Factory Settings, Reset settings and user interface modifications, and Reset entire user profile. I did not have any user extensions installed prior to doing this. I then clicked on Apply Changes and Restart. This seems to have cleared up the issue.
*** Bug 122310 has been marked as a duplicate of this bug. ***
thanks loyde and steven for reporting your solution. Helpful for others too. I close as WorksForMe then.