Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 468935 - "Print to file" on first-use sometimes really prints to the default printer
Summary: "Print to file" on first-use sometimes really prints to the default printer
Alias: None
Product: Fedora
Classification: Fedora
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F10DesktopTarget
TreeView+ depends on / blocked
Reported: 2008-10-28 22:57 UTC by Bill Nottingham
Modified: 2014-03-17 03:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-11-14 15:02:10 UTC

Attachments (Terms of Use)

Description Bill Nottingham 2008-10-28 22:57:30 UTC
Description of problem:

I select 'Print to file', and choose to print.

It prints to the default printer (i.e., not to a file.)

I then select 'Print to file', and choose to print.

It then prints to a file.

Version-Release number of selected component (if applicable):

How reproducible:

Every time

Steps to Reproduce:
1. Print to file
Actual results:

Prints somewhere else (the first time). 

Expected results:

Prints to file.

Comment 1 Caolan McNamara 2008-10-28 23:12:15 UTC
Err..., that's odd and I don't see it myself. 

Is it opening an existing document and using print to file, or writing a new one from scratch. What OOo application, writer or calc or something else ?. Is it when not changing any defaults, i.e. just taking "output.pdf" format "pdf", or twiddling to .ps ?

Maybe there is a race in here wrt. printer detection and using any print functionality.

Comment 2 Bill Nottingham 2008-10-29 01:16:22 UTC
I reproduced this again.

Open document. (Existing document, ooffice <file> Opened in writer.)

Select 'print'. It defaults to my default pritner.

Pick a browsed printer. Final '<print>' button is greyed out. Not sure why.

Select 'Print to file'. Flip it to PS output.

... sent to default printer.

I then tried for more reproductions, and it didn't happen. So, maybe there is a race somewhere.

Comment 3 Caolan McNamara 2008-10-29 09:20:55 UTC
Yeah, I have it. Printer detection hasn't truly finished, so we force it to complete and wait, but the side-effect is that the current "print to file" setting gets tossed out so we end up printing to the default printer. We just need to move setting those properties to after we have the final printer handle.

(Pick a browsed printer. Final '<print>' button is greyed out. Not sure why.)

FWIW, that'd be the dialog itself, not OOo so I'd expect evince (and other users of that dialog) to show the same greyed out button for a printer if OOo shows one. Might be greyed out while waiting for some cups querying of capabilities or something)

Comment 4 Matthias Clasen 2008-10-29 18:54:54 UTC
Marek, can you have a look at this.

Maybe this broke during our latest async changes for default printer handling ?

Comment 5 Caolan McNamara 2008-10-29 22:56:33 UTC
Err.., hang on here. I'm pretty sure the substantive issue is my one and OOo specific.

There may be some generic issue wrt. the greyed out button sceál but the primary info coming from the dialog as to "print to file" being selected is good from gtk2-print-unix

Comment 6 Marek Kašík 2008-11-03 16:44:52 UTC
I reproduced the problem with gtk older than the one in which the default printer handling is changed. So it is not broken by this change.
I reproduced this for printing to PostScript file only and only for documents opened from a disc (not for new documents). It works for PDF for me. So it is probably bug in OOo.
I couldn't reproduce the problem with the greyed out button. Does it show up with "gtk-demo" (the Printing section)?


Comment 7 Caolan McNamara 2008-11-03 16:50:53 UTC
"So it is probably bug in OOo.". Yes, see #3.

Comment 8 Jesse Keating 2008-11-14 18:12:26 UTC
Caolan, why did this get closed?  Was there a new build to fix it, and if so, has it been tagged for the final release?

Comment 9 Bill Nottingham 2008-11-14 18:46:04 UTC
This was fixed in 3.0.0-9.7. F10 currently has 3.0.0-9.10.

Note You need to log in before you can comment on or make changes to this bug.