Bug 56556 - PDF: pdf-export does not take the file name along
Summary: PDF: pdf-export does not take the file name along
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-30 00:47 UTC by bugquestcontri
Modified: 2013-08-21 15:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bugquestcontri 2012-10-30 00:47:25 UTC 
Problem description: 

When exporting an LibO file (e.g. abcd.odt) to pdf, the original file name is not automatically transferred to become the pdf-file name (e.g .abcd.pdf). The field for the file name is empty.

I observed this behavior in 3.5.6 and in 3.5.7. It starts without any recognizable cause and also stops suddenly. Thus,it is currently behaving correctly

Steps to reproduce:
not known yet

Current behavior:
suddenly export to pdf does not carry over the LibO file name and keeps the file name field empty

Expected behavior:
file name of LibO file becomes automatically the file name of the pdf-file created by export to pdf

Platform (if different from the browser): 
XP/SP3         
Browser: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0
Comment 1 Rainer Bielefeld Retired 2012-10-30 06:22:58 UTC 
We already had such an issue if there is not a .pdf in the folder and some other circumstances come together, I do not remember all details.

@bugquestcontri@online.de 
Any chance to get this one 100% reproducible?
Comment 2 bugquestcontri 2012-10-30 15:40:52 UTC 
Just made a test:

doc-file and odt-file: pdf-export into 2 different empty folders - names were carried over properly

I will watch to see what could have caused this problem and report.
Comment 3 bugquestcontri 2013-03-06 03:21:06 UTC 
I still have to confirm the bug in Version 3.6.5.2 (Build ID: 5b93205)
but I never could identify the trigger. 

I will keep watching and report.
Comment 4 tommy27 2013-08-18 18:35:56 UTC 
I do not reproduce it on LibO 4.0.4 (Win7 64bit)
setting this as RESOLVED WORKSFORME.
hopefully it was just a bug of the old 3.5.x branch.
Comment 5 bugquestcontri 2013-08-21 15:45:48 UTC 
I will see if it pops up again. I am now at 4.0.4.2 and will reopen if I find it again.