Closed Bug 806357 Opened 13 years ago Closed 10 years ago

Print to file (pdf) function ignores the user selected directory when user renames the default file name from mozilla.pdf to something else.

Categories

(MailNews Core :: Printing, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: peter.vilhan, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121025212310 Steps to reproduce: 1. Open the received email 2. Click on other actions, print 3. select Print to File printer 4. click on save in folder select box and select Other 5. go to the directory where you wan't to store pdf file and click on Open button 6. Change the name of the generated pdf file in the Name input text box. 7. Click on Print Actual results: File is stored with correct name but on incorrect place, in user Home directory. So the program ignored the user defined directory. Expected results: File should have been saved in user defined directory.
Component: Untriaged → Printing
Product: Thunderbird → MailNews Core
I experience the same bug with Firefox 18 (x86_64, as packaged in Fedora 17) so I guess this bug concerns anything that uses the print dialog.
Aki Koskinen: https://bugzilla.mozilla.org/show_bug.cgi?id=923041 seems to be your bug (no idea if it's the same as this one)
Related (Duplicate) Bugs: Bug 806357, Bug 845425, Bug 865416, Bug 923041 Bug 923041 seems like the most accurate description from my experience. Bug 845425 concluded that it was a gtk+ issue, not Mozilla issue. See also: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1213385 https://bugzilla.redhat.com/show_bug.cgi?id=888080
bug 865416 recently closed WORKSFORME. Do you still see this problem?
Flags: needinfo?(peter.vilhan)
Whiteboard: [closeme 2015-02-25]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(peter.vilhan)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2015-02-25]
You need to log in before you can comment on or make changes to this bug.