Created attachment 45794 [details]
Screenshot of error message
I try to open writer and I get this error message:
General input/output error.
It doesn't matter if I try to start writer from the startcenter (as shown in the screenshot) or I manually try to open swriter.exe, I get the same error message. This bug was originally Bug 36271 but that has morphed into the bug which deals with opening files. Either way, they are related as the same error message occurs.
I tried the instructions as proposed by Allen in Bug 36271 which read:
(In reply to comment #14)
> Could the users who are seeing this problem (or a related problem) try the
> 1. Run LibreOffice to confirm the problem.
> 2. Close LibreOffice.
> 3. If the LibreOffice Quickstarter is running, right-click on the LibreOffice
> Quickstarter icon in the system tray and select "Exit Quickstarter".
> 4. Run taskmgr (Start -> Run -> type "taskmgr" and hit Enter).
> 5. Verify that there are no processes running with names that start with
> "soffice" (such as "soffice.exe" or "soffice.bin").
> 6. Navigate to your user setting directory (open the Windows File Explorer,
> type %APPDATA$ in the location bar and hit Enter).
> 7. You should see a subfolder called "LibreOffice". Rename this subfolder to
> something else, like "LibreOffice-save".
> 8. Run LibreOffice and check to see if the problem is still occurs.
> If the problem is still there, do the following if you are running Vista or
> Windows 7; otherwise, skip to Step 14 below:
> 9. Repeat Steps 2-6 above, and then:
> 10. In your user settings directory, delete the subfolder named LibreOffice.
> 11. Navigate to your VirtualStore folder, which is at C:\Users\<your
> 12. Look in all subfolders for any subfolders named "LibreOffice" or
> "LibreOffice 3", and if you find one, delete it.
> 13. Run LibreOffice and check to see if the problem is still occurs.
> If the problem is still there:
> 14. Repeat Steps 2-6 above, and then:
> 15. In your user settings directory, delete the subfolder named LibreOffice.
> 16. Uninstall LibreOffice.
> 17. Delete the folder named "LibreOffice 3" in the Windows programs directory
> (either "C:\Program Files\LibreOffice 3" or "C:\Program Files (x86)\LibreOffice
> 3", depending on whether you are running a 32 bit or 64 bit version of
> 18. Reboot your computer.
> 19. Reinstall LibreOffice.
> 20. Run LibreOffice and check to see if the problem is still occurs.
> If any of the above helps, please post which step solved the problem.
Step 7 solves the problem and allows writer to run. However, upon exiting LO (doesn't matter what component is running) soffice.exe crashes every time.
Hope some of this helps!
I still suspect that
"Bug 36271 - FILEOPEN impossible, General error, memory could not be read"
has the same roots
> However, upon exiting LO (doesn't matter what component is running) soffice.exe crashes every time.
That is a different bug and IMO should be handled on a different thread. It might be the same as the "Error reading memory" that others are reporting.
> Step 7 solves the problem and allows writer to run.
OK, there is something in your %APPDATA%\LibreOffice folder that is preventing Writer from running. I have no idea what that might be though, and just to warn you, tracking down the specific item might be about ten times more work than you've expended so far. If you have the time though, it might be helpful if you close LO (Steps 1-5 of the troubleshooting procedure I posted), delete your new %APPDATA%\LibreOffice folder and then rename your defective folder %APPDATA%\LibreOffice-save back to %APPDATA%\LibreOffice. Then attempt to run Writer and confirm you are getting the bug. Finally, follow my procedure on your earlier bug report #36271 to generate a ProcMon dump file, upload that file somewhere and post a link where I can download it and take a look.
Zack, Tor's recent comments on a number of different bugs indicate that some serious and potentially related problems in LO v3.4 Beta 1 have already been fixed. Given the level of effort that would be required to track down the specific source of your problem, as well as a availability of a work around (deleting the %APPDATA%\LibreOffice directory), I think it would make sense at this point to wait for a LO v3.4 Beta 2 release and see if that resolves this problem, before attempting to troubleshoot further.
I cannot reproduce this problem in a fresh install of a fresh build of the libreoffice-3-4 branch. Comment #3 probably is useful, there might be something in your user-specific settings that causes the problem. Do you think you could zip up the %APPDATA%\LibreOffice folder and attach to this bug? Please check that nothing confidential gets included.
(In reply to comment #5)
> I cannot reproduce this problem in a fresh install of a fresh build of the
> libreoffice-3-4 branch. Comment #3 probably is useful, there might be something
> in your user-specific settings that causes the problem. Do you think you could
> zip up the %APPDATA%\LibreOffice folder and attach to this bug? Please check
> that nothing confidential gets included.
I'm going to wait for Beta 2. Based on the error message I agree that this may be related to Bug 36263 as well.
(In reply to comment #2)
This only occurs when attempting the workaround of deleting/renaming the %APPDATA%\LibreOffice folder.
I will close this bug for now and await the Beta 2. If the problem resurfaces I'll reopen and attach the contents of my %APPDATA%\LibreOffice folder and we can go from there.
Thanks for all the hard work!
This has been fixed in Beta 2.
Remove infoprovider from closed and resolved bugs.
RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO.
If you are facing this kind of issue, This issue can be generate many reason like missing file or corrupted. For avoid this issue check it https://unfitpc.com/swriter-exe and i am sure that it would really help you. You can download the missing file.