Hi! I think I found a bug: Working with a file from samba and option "Always create backup copy" (tools -> options -> Load/Save -> General) always leads to the error: Error saving the document <file>: Error creating object. Could not create backup copy. the backup file _is_ created but zero bytes: ls -l ~/.config/libreoffice/3/user/backup/ -rw-r----- 1 <user> <group> 0 Sep 17 12:02 <file>.bak Option disbled: works local file instead of samba file: works thanks! greets, Martin
Hello Martin, *, have you tried a newer version of LO than 3.6.0.4? Does your problem occurs there, too? I have no samba here to test, so this is only a little reminder ... ;) If you error still occur: 1. Could you give us some more details like with distro on what archtecture are you using? 2. How do you connect your samba client to the server? And which samba version on the client and server are you using? 3. Which OS do you want to use via samba? 4. Would you be so kind to start LO from commandline to see, if there is any error message, please? And maybe with "soffice --backtrace" and attach the backtrace log to this bug? Sorry for the inconvenience Thomas.
(In reply to comment #1) > Hello Martin, *, > have you tried a newer version of LO than 3.6.0.4? Does your problem occurs > there, too? I have no samba here to test, so this is only a little reminder > ... ;) Same error using Version 3.6.6.2 (Build ID: 3.6.6.2-9.fc18) > > If you error still occur: > 1. Could you give us some more details like with distro on what archtecture > are you using? Ubuntu when I reported the bug, fc18 now. > 2. How do you connect your samba client to the server? And which samba > version on the client and server are you using? cifs mount (replaced some private parts with '*'): //samba.*****.de/home on /samba type cifs (rw,nosuid,nodev,noexec,relatime,vers=1.0,sec=ntlmssp,cache=strict,unc=\\samba.***domain****\home,username=****,domain=****,uid=1000,forceuid,gid=0,noforcegid,addr=***IP***,file_mode=0644,dir_mode=0755,nounix,rsize=61440,wsize=65536,actimeo=1) > 3. Which OS do you want to use via samba? ? Don't get it: client is Linux fc18, server is Red Hat Enterprise Linux Server release 6.1 (Santiago) samba-3.5.6-86.el6_1.4.x86_64 > 4. Would you be so kind to start LO from commandline to see, if there is any > error message, please? And maybe with "soffice --backtrace" and attach the > backtrace log to this bug? soffice --backtrace GNU gdb (GDB) Fedora (7.5.1-38.fc18) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib64/libreoffice/program/soffice.bin...Reading symbols from /usr/lib/debug/usr/lib64/libreoffice/program/soffice.bin.debug...done. done. log will be saved as gdbtrace.log, this will take some time, patience... (gdb) less gdbtrace.log warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". warning: "/usr/lib/debug/usr/lib64/libicudata.so.49.1.1.debug": separate debug info file has no debug info [New Thread 0x7ffff7fa3700 (LWP 6496)] [New Thread 0x7fffedb44700 (LWP 6497)] [New Thread 0x7fffed343700 (LWP 6498)] [New Thread 0x7fffe6c56700 (LWP 6501)] [New Thread 0x7fffe5ad9700 (LWP 6502)] [New Thread 0x7fffe5217700 (LWP 6503)] Detaching after fork from child process 6504. [New Thread 0x7fffd3fff700 (LWP 6506)] [Thread 0x7fffd3fff700 (LWP 6506) exited] [Thread 0x7fffedb44700 (LWP 6497) exited] [New Thread 0x7fffedb44700 (LWP 6525)] [New Thread 0x7fffd3fff700 (LWP 6526)] [New Thread 0x7fffd1483700 (LWP 6527)] [Thread 0x7fffd3fff700 (LWP 6526) exited] [Thread 0x7fffd1483700 (LWP 6527) exited] [New Thread 0x7fffd1483700 (LWP 6528)] [New Thread 0x7fffd3fff700 (LWP 6529)] [Thread 0x7fffd1483700 (LWP 6528) exited] [New Thread 0x7fffd1483700 (LWP 6538)] [Thread 0x7fffd3fff700 (LWP 6529) exited] [Thread 0x7fffd1483700 (LWP 6538) exited] [New Thread 0x7fffd1483700 (LWP 6539)] [New Thread 0x7fffd3fff700 (LWP 6540)] [Thread 0x7fffd3fff700 (LWP 6540) exited] [New Thread 0x7fffd3fff700 (LWP 6541)] [Thread 0x7fffd3fff700 (LWP 6541) exited] [Thread 0x7fffd1483700 (LWP 6539) exited] [New Thread 0x7fffd1483700 (LWP 6542)] [Thread 0x7fffd1483700 (LWP 6542) exited] [New Thread 0x7fffd1483700 (LWP 6545)] [New Thread 0x7fffd3fff700 (LWP 6546)] [Thread 0x7fffd3fff700 (LWP 6546) exited] [Thread 0x7fffd1483700 (LWP 6545) exited] [New Thread 0x7fffd1483700 (LWP 6547)] [Thread 0x7fffd1483700 (LWP 6547) exited] [Thread 0x7fffe6c56700 (LWP 6501) exited] [New Thread 0x7fffe6c56700 (LWP 6548)] [Thread 0x7fffe6c56700 (LWP 6548) exited] [New Thread 0x7fffe6c56700 (LWP 6549)] [Thread 0x7fffe6c56700 (LWP 6549) exited] [Thread 0x7fffed343700 (LWP 6498) exited] [Thread 0x7fffe5217700 (LWP 6503) exited] [Thread 0x7ffff7fa3700 (LWP 6496) exited] [Thread 0x7fffe5ad9700 (LWP 6502) exited] [Thread 0x7ffff7fb4980 (LWP 6492) exited] [Inferior 1 (process 6492) exited normally] /usr/lib64/libreoffice/program/gdbtrace:8: Error in sourced command file: No stack. Missing separate debuginfos, use: debuginfo-install gtk2-2.24.18-1.fc18.x86_64 quit unfortunately this seems to be not available: ~>sudo debuginfo-install gtk2-2.24.18-1.fc18.x86_64 [...] No debuginfo packages available to install
Hello Martin, *, (In reply to comment #2) > (In reply to comment #1) > > have you tried a newer version of LO than 3.6.0.4? Does your problem occurs > > there, too? I have no samba here to test, so this is only a little reminder > > ... ;) > > Same error using Version 3.6.6.2 (Build ID: 3.6.6.2-9.fc18) have you tried one of the 4.x builds (either the stable 4.0.4 or the dev build 4.1.0.1RC)? > > If you error still occur: > > 1. Could you give us some more details like with distro on what archtecture > > are you using? > > Ubuntu when I reported the bug, fc18 now. Thanks for your info :) > > 2. How do you connect your samba client to the server? And which samba > > version on the client and server are you using? > > cifs mount (replaced some private parts with '*'): OK > //samba.*****.de/home on /samba type cifs > (rw,nosuid,nodev,noexec,relatime,vers=1.0,sec=ntlmssp,cache=strict, > unc=\\samba.***domain****\home,username=****,domain=****,uid=1000,forceuid, > gid=0,noforcegid,addr=***IP***,file_mode=0644,dir_mode=0755,nounix, > rsize=61440,wsize=65536,actimeo=1) As I have not the knowledge about samba, I let this to comment from one of the devs ... ;) > > 3. Which OS do you want to use via samba? > ? Don't get it: client is Linux fc18, server is Red Hat Enterprise Linux > Server release 6.1 (Santiago) > samba-3.5.6-86.el6_1.4.x86_64 That's the info, I wanted to get ... ;) Thanks :) > > 4. Would you be so kind to start LO from commandline to see, if there is any > > error message, please? And maybe with "soffice --backtrace" and attach the > > backtrace log to this bug? <snip> I snip the backtrace part, but hopefully one of the devs find something useful in it ... ;) > [Inferior 1 (process 6492) exited normally] > /usr/lib64/libreoffice/program/gdbtrace:8: Error in sourced command file: > No stack. > Missing separate debuginfos, use: debuginfo-install > gtk2-2.24.18-1.fc18.x86_64 > quit > > unfortunately this seems to be not available: > > ~>sudo debuginfo-install gtk2-2.24.18-1.fc18.x86_64 > [...] > No debuginfo packages available to install But maybe there is one gtk2-2.24.18-1.fc18.dbg (debug) package in the repository, which is missing ... ;) Sorry for the inconvenience Thomas.
> have you tried one of the 4.x builds (either the stable 4.0.4 or the dev > build 4.1.0.1RC)? Just installed fc19 on different machine: libreoffice-core-4.1.0.1-3.fc19.x86_64 same error: Samba + "Always create backup copy" does not work. greets, Martin
Hi marting, We met same issue on Windows, but this has been fixed recenntly. Directory for backup was mssing. Please see: Bug 65501 - FILESAVE Can not save a modified document with backups enabled Thank you, Jacques
It is a bit of a disappointment, that this bug has been creeping around since 2006. </rant> I can confirm this. And I fail to have a good workaround. And I can confirm that the backup directory exists. And I can add some remarks: 1. It always works when I save to a new file name on the folder (mounted cifs) 2. It never works when I 'save' to the then existing file name. The .bak is actually created, on the local drive, but with a size of 0. Then it fails to update the file on the shared folder. 3. The best of the worse workarounds: I create two almost identical files on the drive, and 'toggle' to which I store; because if I have file1 open and work on it, I can always save as file2, and when I have file2 open, I can always save as file1. But having file1 open, I cannot save to file1 without the error message coming up; same with file2. Conclusion: it only fails if one wants to store to the same, open, file.
*** Bug 62556 has been marked as a duplicate of this bug. ***
*** Bug 67827 has been marked as a duplicate of this bug. ***
Changed version to oldest known (from bug 62556)
CONFIRMED here with LO 4.0.3 and LO 4.1.2.3 on Linux Mint Debian Ed., also on Win7. Didn't really notice it with LO 3.x before, but now it is permanent: Editing and saving a writer or calc file on a local ext4 or NTFS disk works; the backup file on a local NTFS disk is correctly created. All fine so far. Editing and saving a writer or calc file on a CIFS mount (our common file server) fails with "Backup could not be created" while the backup file is created with a size of 0 (regardless whether it existed before or not). Saving with backup disabled works. Moving my ~H:/config/libreoffice/4 and /3 away (thus forcing LO to create a new blank profile) does not help. I regard this as a rather severe bug since it effectively blocks the use of the backup feature! Because of this bug I just upgraded to 4.1.2.3, but to no avail. Hans
FWIW: our CIFS server is openSUSE 12.1, Samba version 3.6.3-34.11.1-2788-SUSE-SL12.1-x86_64 with unix extensions = no
*** Bug 80539 has been marked as a duplicate of this bug. ***
Two years now and no response…? I'd like to raise Importance to Major, since this bug effectively blocks LO from using backup files in a company environment! Hans
+1 It's huge inconvenience in a corporative environment/
(In reply to comment #14) > It's huge inconvenience in a corporative environment/ Indeed. There are ways to solve this for those that do not want to wait for .. Question: did this work before version 3.6.5.2 ? thanks, Cor
(In reply to comment #15) > Indeed. There are ways to solve this for those that do not want to wait for Ehm… which ways? (Please don't say MS Office) > > Question: did this work before version 3.6.5.2 ? Yes, we did use it with some Version 3 — don't know exactly which one, probably 3.3. Hans
Hi Hans, (In reply to comment #16) > > Indeed. There are ways to solve this for those that do not want to wait for > > Ehm… which ways? (Please don't say MS Office) Ha - of course not. But some larger organisations maybe could afford to hire a certified dev for this, or take a 3rd level support contract entitling for buxfixing. http://www.libreoffice.org/get-help/professional-support/ I'm not suggestion that this is the only way for bugs to get solved, nor that it should be that way. But it is a clear route, supporting paid development. And of course, anyone knowing/being a developer that has feeling with this area.. > > Question: did this work before version 3.6.5.2 ? > > Yes, we did use it with some Version 3 — don't know exactly which one, > probably 3.3. Some version 3... But LibreOffice or our predecessor? Thanks, Cor
As I remember this bug was already in 2011 year. I did ask advice on it from one of my friends in e-mail. What version was I don't remember. Eugene
(In reply to comment #17) > Some version 3... But LibreOffice or our predecessor? Oh — right, that must have still been OOo then. Hans
> Some version 3... But LibreOffice or our predecessor? I just found in my notes that I reported this bug for OOo-2.x WBR Eugene
(In reply to comment #20) > I just found in my notes that I reported this bug for OOo-2.x Thanks Eugene
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.