Recently went to open .ods files that I have never had problems with. When trying to open, calc will come up but hang and never completes opening the file. The files open fine with zip utilities as well as with LibreOffice on other OS (Linux).
It appears to be this computer and not necessarily LibreOffice itself. If there are any ways to debug please let me know and I will provide additional information. I will upload a sample file shortly that suffers from this issue. Note that new files that are saved and some old files do not appear to be affected.
Created attachment 53252 [details]
Example file that causes Calc to hang
I have an .xls that opens fine. I saved said .xls as an .ods and tried to re-open it with Calc, and Calc hangs. This file opens fine in Calc on Linux.
try to backup your user profile, delete the existing one and thenre start calc and try to open the file again
might just be a corrupted user profile dir
Where is the user profile stored in Windows 7?
I attempted a complete uninstall/reinstall before I posted the bug:
- Uninstall all Libreoffice
- Uninstall all Visual C++
- Uninstall all Java
- Remove everything I could find (Program Files (x86), Program Data/Libre Office, AppData/Roaming/Libreoffice, etc).
The problem persisted, which is then why I posted the bug.
Are there any debug modes or other logging that I can do on Windows here?
I had also run cccleaner and performed windows updates before reinstalling Libre.
Fault bucket , type 0
Event Name: AppHangXProcB1
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 32fb2eb2-098b-11e1-a8d7-0030675a3caf
Report Status: 1
What an annoying problem. I figured out the fix.
Someone on IRC suggested that spoolsv had to do with printers:
17:09 <julien2412> spoolsv.exe is a Microsoft Windows system executable which
handles the printing process to your local printers.
After some sleuthing, I realized that I have a network-connected printer that
was offline. Apparently this makes Windows 7 *extremely* angry. After much
dorking around, I was able to remove this printer.
Guess what? Calc starts up just fine!
This leads me to believe that there is a more sinister issue at hand. Why
would .xls files and .odt files open just fine, but .ods files hang? What was
it about this particular file that caused Calc to really want to get down with
the printers and to hang because this printer was not connected?
I will change the title of the bug.
This is on Win7 x64 Ultimate.
I am marking this ticket as resolved. The issue was resolved by you removing the printer on your network.
The application have been unable to open the file due to an existing lock on the file by another application.
"The application have been unable to open the file due to an existing lock on
the file by another application."
Which application? Calc was the only program not able to open the file, and calc hung hard. If the file was simply locked, the expectation would be for calc to report that "this file is in use by another application."
At best, this is an issue with how Calc handles file locking.
At worst, this is an issue with how Calc interacts with the print stack on Windows.
Saying that it's not a bug because removing the printer fixed the issue is folly. The resultant implications are that:
* Temporary printer outages mean that Calc may at any moment be unusable. I guess printers never go down?
* Users who travel between multiple locations (home/office, etc) and have printers in each location will have to remove and reinstall printers before leaving the previous location so that calc will work.
Does this sound like it makes any sense to you?
I would add that the latest version of calc hangs for a long time and then crashes on loading an ods file unless your network printer is turned on.
Took me most of the night to figure out what the heck was wrong as it was working fine earlier in the week (when the printer was on). I tried upgrading and bunch of other stuff to no avail.
It wasn't until I accidentally picked print in another application that sitting there watching the pin wheel to time out triggered a memory about issues that power point has with off network printer
and made me think maybe that we my libreoffce problem too. Sure enough.
I'm re-opening in hopes you will reconsider if for no other reason that libreoffice doesn't just hang but actually crashes now too.
PS: I'm running 18.104.22.168 Build ID: c4c7d32d0d49... on Windows Vista.
Bug does not meet the criteria for Status 'REOPENED'
Status -> NEEDINFO
Tyson: is this still a problem with LibO 5?
Set to NEEDINFO.
Change back to NEW, if the problem persists (as this is confirming an older report). Change to RESOLVED WORKSFORME, if the problem went away.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Sun, 11 Sep 2016 21:43:24 +0200
Hello, jumping in because I have this issue with Windows 10 Pro v1607 and LibO 5.2.2. 64bit (that's why I changed Hardware from x32 to all).
When opening local simple ods files, Libreoffice shows an undecorated empty and unresponsive window for about one minute. Digging with sysinternals Process Monitor, I see it continuing right after having loaded the printer spooler dll (ps5ui.dll), having dealt with printers when starting to be unresponsive. I have network printers not connected at this moment, that use the Postscript interface, so I guess Libreoffice hangs waiting for Windows loading the spooler ui dll, but that is clearly not the intended behavior.
I would expect to load the spooler dll from a non blocking thread while proceeding to open the file would solve this issue - showing an empty hanging windows to the user should never happen.
I am having the same issue with LibreOffice_5.2.7_Win_x86 under Windows 8 x64.
When I load a file in Calc, it hangs for up to 2 minutes with the windows "Loading wheel icon" and becomes completely unresponsive. Afterwards it works
My main printer is a network printer that is usually offline. No issues if the printer is online.
Here is someone else with the same issue -
Like them, If I stop the windows process splwow64.exe as Calc is being unresponsive, calc resumes instantly (it becomes responsive) -
Or, if I do "ipconfig /release" while Calc is being unrespnsive, it instantly becomes responsive.
To be clear, loading any Calc file in Calc causes this, not a specific file. Also, this freezing does not seem to happen if I load Libreoffice and click CREATE - Calc Spreadsheet.
Only loading an existing file.
Also, this does NOT happen if I load an existing .xlsx file in Calc, only .ods
I could fix an ods whcih hangs when network printer was unavailable.
There is a section in ods (renamed to zip and extract settings.xml file from it) where the printer related option stored.
My netowork printer adreess was: \\192.168.1.11\lp
If I delete printer related data section from settings.xml ods file opens like a charm even the network printer is unavailable :)
So delete XML data tags: PrinterName and PrinterSetup (whole xml data tags)
(of course make a backup from ods 1st)
In My case the printer was an usb printer connected to my NAS and it was used by some Windows machines on home network.
When the NAS was turned off (or its LAN cable unplugged)
ods files freezed at opening.
In Calc File/Printer settings without deletion I could see the old network printer IP, after deletion there I could see my current default printer (also a network printer but connected to my router) however the settings.xml did not have the deleted tags.
So the final fix should be using some timeout at opening or a popup window about unavailable network printer and an option to delete old printer info from ods.
LO version 22.214.171.124 x64 & WIN10 Pro
I wanted to add that this freezing can happen with an opened document that I'm editing, when I do certain tasks like highlight data and Ctrl-Rightclick-Format cells. Sometimes (not always) that action can freeze for 30 seconds before the Format cells dialog comes up. Again this won't happen if my network printer is ONLINE only when it is OFFLINE.
szz, I tried your trick but it did not work for me. (Although I do see mentions of an offline printer in many of my .ods files)
szz, actually I think I spoke too soon. I think you're right. If I set my default printer to the "windows XPS writer" and create a new .ods, that file loads fine and has no issues. Only the files I created when my network printer was default have freezing issues .
a partial fix: Load the file, pick File-> Printer Settings and select "Microsoft XPS Document Writer" or some other non-network printer, then re-save the file.
however there is still some freezing if your windows default printer is set to a offline network printer, despite doing the above. But it helps somewhat.
Calc hang on open any ods files until I cleared print queue and completely removed virtual printer (ImagePrinter) from OS. The queue appeared from some bug in that printer during printing a .pdf file into images by other software (not LO).
*** Bug 116559 has been marked as a duplicate of this bug. ***
I have the same problem under Linux (Ubuntu 16.04 x86-64) with LO 6.1.4 and network printers not reachable. If I disconnect my PC from the network, Calc opens the file instantly.
Best regards. JBF
I have the same problem on Windows 10 (version 1903 and 1809). When network printer is disconnected Calc hangs opening any files, I've tried couple version 6.2.x, 6.1.x and 6.0.x.
Created attachment 152615 [details]
soffice.bin wait chain with spoolsv.exe
I also encountered this problem today and it took a long time to find the root cause. I have some additional details to share.
I did a clean install of Windows and found that LibreOffice Calc would take 13 seconds to open even the most basic ODS files while this didn't happen before. XLSX files worked just fine. I tried everything from reinstalling LibreOffice to removing the profile directory with no result. I finally reinstalled Windows again and kept track of when LibreOffice Calc would stop working. I found that it started occurring when I installed the printer (Epson XP 630) through Windows and the printer was offline, and found this bug.
Like others noticed above, ODS files (for most likely a good reason) contain a reference to the printer, so I presume LibreOffice Calc is trying to locate this printer upon startup. Unticking the "Load printer settings with the document" as suggested in https://bugs.documentfoundation.org/show_bug.cgi?id=116559 did not work for me, but what did work was changing the default printer to e.g., the Microsoft XPS Writer.
I looked into this and found that Windows installed the default Microsoft IPP drivers for the printer instead of the Epson drivers, and I can only assume that the spooler keeps on trying to connect to the printer even though it's offline. The moment I installed the Epson-specific drivers, the problem was gone. I guess it has a faster way to tell the spooler that the printer cannot be reached.
I would say that Windows is at fault for not installing the Epson drivers by default and for having a default driver that apparently makes the spooler wait for a long time before reporting that the printer is offline. However, I agree with Comment 13 that LibreOffice Calc can mitigate the issue by querying the spooler in a separate thread. Removing the spooler actions from the main thread would allow the rest of LibreOffice Calc to work correctly and the document to open normally, while in the background the spooler is queried. This would make the issue invisible for the user because having to wait 10+ seconds for a document to open is too long.
I'm hoping this will help to get the issue resolved. Thank you for all your work on LibreOffice!