I recently got this write error in OO.org. The file could not be written. The file could not be written. The copy / paste method would have changed too many things (some fonts changed).What seems to have happened is that there is a file in /tmp (I'm on Linux) that OO http://vbview.net/openoffice-error/openoffice-error-saving-document-access-denied.php
by jackua » Thu Dec 01, 2011 3:10 am I have had this problem for years when left the office running for very long time. The file could not be written. The aplication freezes.Otherwise, i can save files in doc or rtf format.I'm using Arch 64, gnome desktop and i test with all the possibilities readed at forum:purge /home/.openffice, reinstall openoffice, version I'm not sure if this is an OpenOffice, file system, Fedora or permissions issue though I've not noticed anything similar with other applications. https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=23218
Nearsited Posts: 1Joined: Mon Nov 07, 2011 7:54 pm Top Re: Write Error. AOO 4.1.3 on Xubuntu 16.10, (Yakkety Yak) and PortableApps port 4.1.2 on Windows 7 Hagar Delest Moderator Posts: 26996Joined: Sun Oct 07, 2007 9:07 pmLocation: France Top Re: Write Error. There are many comments about it happening on documents which have remained open for extended periods of time. Discuss the word processor Post a reply 21 posts • Page 1 of 1 Write Error.
I have found that the problem occurs after some period of time, no specific activity by the user is required to generate the error. The file could not be written. by racitup » Wed May 25, 2011 8:00 am Hi all,I recently upgraded to LibreOffice 3.3.2 from OpenOffice 3 (version 3.2.0?) on Linux Ubuntu 10.04 LTS.It has been working fine (apart Or perhaps someone has temporarily removed the floor under your bed."MSI MegaBook GX600P-208NL Offline #7 2009-02-11 20:01:03 AndyRTR Developer From: Magdeburg/Germany Registered: 2005-10-07 Posts: 1,640 Re: [SOLVED]I can't save files in
Comment 14 justinholland 2007-08-20 02:13:40 UTC I also have the zero size backup files, this may be normal. Comment 9 Olaf Felka 2007-08-10 19:25:05 UTC It's hard to take some action on this issue if nobody who should fix has a chance to reproduce. Unfortunately, no one has posted a way to reproduce the problem. navigate here I do not think the problem is because the temp file is full or presumably I would not be able to save the new copy.
The file could not be written. Are you trying to save to a networked location (e.g., Windows or NFS share)? This is a very large hit to my productivity. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page...
I use Windows Vista x86 platform. If you periodically save a file, close it, and reopen it, you can avoid this bug."Another note is "Update: in this instance, with Writer giving the error, I was able to Some of the files in the backup folder are normal .odt files or normal .bak files but several are appearing with a size of zero and a double extension , for I would be nice to have someway to force a debug or memory dump when the problem occurs.
Thanks! his comment is here Any "too clever" stuff like selinux running? The file could not be written. raffe Using Fedora 2 27th April 2005 06:48 PM Current GMT-time: 20:25 (Thursday, 01-12-2016) All trademarks, and forum posts in this site are property of their respective owner(s).
it seems that this has something to do with the protection of the /tmp directory (which i did not want to explore further). The fix that worked for me was to export (File, Save As...) as a .SXW files then open this new doc and export to .ODT Worked for me - hope it not very elegant, but it does work. this contact form OpenOffice 3.1.1 on Linux RH5.5 jackua Posts: 1Joined: Thu Dec 01, 2011 3:02 am Top Re: Write Error.
I will happly to turn on debug flags or whatever if some developer wants to work with me. I've also discovered that the backup is also corrupted making recovery even more critical. It is a great comfort to find that I am not the only person with the problem.
I open an ODS file and edit it and save, fine. It contains information that I can't afford to lose. Board index The team • Delete all board cookies • All times are UTC + 1 hour [ DST ] Forum powered by phpBB © phpBB Group By any use of I have to kill/exit the program and restart.I will update cron jobs and wait for a month or two to see if it helps.
Because Writer doesn't crash it won't generate any error reporting so it's hard to resolve. If I save document after every small operation (e.g. by Nearsited » Mon Nov 07, 2011 8:00 pm Reduce the number of rows/worksheets. http://vbview.net/openoffice-error/openoffice-error-name.php It would really help indeed if you've found a file that replicates the problem.
I'm going to post another issue involving the Synaptic Package Manager which occurred at the same time this issue came up. Perhaps a way to fix a broken installation? Then copy/paste changes to temp.ods. As far as I can tell, its the auto-save failing that causes this "could not be written" error. (for some reason, the auto save always tries to start up when I
Marcus (mark-westrick) said on 2008-09-10: #3 The document is saved as a .odt but when I try to save it I get the error codes given above. I was able to save it both as a odt doc & MS word doc but when I bring the document back into my notebook it will not allow me to I was happily working on a not too complicated spreadsheet (originally created with Excel 2003) that has 5 subsheets with various links between them. Home | New | Browse | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] User community support forum for
I still do some of this, keeping up on technology, tools, and trying to stay bleeding edge. (There's too many edges though.)I like to know how things work, including the internet, thanks for replies. __________________ Not a Linux Guru - please be nice :) Home | Linux adventures DaFoot View Public Profile Visit DaFoot's homepage! Comment 8 iuc 2007-08-10 18:46:47 UTC We too are getting this error after installing 2.2.1. Then try opening the new file.