Suppose I have a.odt and b.doc in some directory. I open a.odt and click save as to convert it to a.doc . However, when I choose doc from the pull-down list, the file name is changed from a.odt to b.doc instead of a.doc . If I do not notice this, the unrelated file b.doc will be overwritten with the converted a.odt without a warning. The reason seems to be that the file dialog is looking for an existing *.doc file instead of creating a new file with the same base name and a different ending.
LibreOffice 4.3.3.2 release Ubuntu 14.04 x64 I do not see this behavior if I am understanding you correctly. What I did: Repro Steps: 1. New document; 2. Save as a.odt in folder temp; 3. New document; 4. Save as b.doc in folder temp; 5. Close LibreOffice; 6. Open a.odt 7. File -> Save As -> Pull Down menu .doc You Observe: File a.odt changes to b.doc? I observe: Extensions aren't even visible - I just see "a" and the extension is controlled by the drop-down. Am I missing something? Setting to NEEDINFO as the instructions provided are a bit unclear. Once you provide reproducible steps please set to UNCONFIRMED. Thanks!
(In reply to Joel Madero from comment #1) These steps are precisely what I meant. I tried again on 2 systems and it is confusing: * With LO 4.2.5.2 on Windows 7 the problem does not happen; the ending is not shown at all but the new file is correct. * With LO 4.1.6.2 on Suse Linux, the problem does not happen in this way in a new directory. The endings are shown, sometimes a.odt is replaced with an empty string upon choosing doc, sometimes a.doc comes correctly. * In my Downloads directory with 2000 files and hundreds of odt and doc , the problem happens consistenly: for several odt files that I tried, the conversion always is changing the file's base name to an existing doc file. The problem does not happen for conversion from doc to odt . * So I copied all doc and odt files to a new directory, but here the problem does not appear ...
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.