Bug 34630 - Name of document name not presetted in directories without PDF files
Summary: Name of document name not presetted in directories without PDF files
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version: 3.3.1 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-23 08:51 UTC by Eric TheThird
Modified: 2012-08-31 10:03 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Eric TheThird 2011-02-23 08:51:36 UTC
The problem exists in OOO 3.2, LO 3.3 and LO 3.3.1 on Windows XP machines.

1) Create a new directory
2) Create a test document and save it (not closing the file).
3) Press 'Export PDF' file action. 
4) An export file dialog is displayed, but the filename of the document is not presetted in the filename entry field. 

If any single PDF file exists in this directory, then the filename of the current file is presetted in the filename entry field.  So this problem only exists for directories without any PDF files in it.
Comment 1 tester8 2011-02-23 10:54:58 UTC
Not reproduced with LO 3.3.1 RC2 Ubuntu 10.04 x86.
Comment 2 Eric TheThird 2011-02-23 12:27:17 UTC
(In reply to comment #1)
> Not reproduced with LO 3.3.1 RC2 Ubuntu 10.04 x86.

I assume its an Windows specific problem with the filedialog.
Comment 3 Björn Michaelsen 2011-12-23 11:43:24 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 Florian Reisinger 2012-08-14 13:57:34 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 13:58:54 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:03:27 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:05:42 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian


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.