Open Bug 1719476 Opened 3 years ago Updated 3 years ago

Always have to send print job twice upon opening firefox, with Citizen CT-S310II receipt printer

Categories

(Core :: Printing: Setup, defect)

Firefox 89
defect

Tracking

()

UNCONFIRMED

People

(Reporter: trishap, Unassigned, NeedInfo)

References

Details

(Keywords: regression, Whiteboard: [old-ui+])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

Every time we open firefox we have to send the first print job twice before it will print anything

Actual results:

Nothing the first time prints fine the second time

Expected results:

Should print the first time sent

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Setup' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Printing: Setup
Product: Firefox → Core

Thanks for the bug report! This sounds very odd/unexpected.

Could you provide a bit more information? In particular, here are some questions that come to mind, but any additional information you can provide would be helpful:

(1) Did this just start happening recently before you filed this bug, or has it been happening for a while?
(2) What printer model are you printing to, and are you connected directly (via USB), or is it a network printer?
(3) Does this happen with basic pages like https://www.example.org/ ? (good simple test page)
(4) It looks like you're using Windows 10 -- is that correct? (or maybe Windows 7?)
(5) Does it work correctly on the first try if you use "Save to PDF"?
(6) Could you visit the special page about:support (type "about:support" into your URL bar and hit your Enter key), and scroll down to "Modified Print Settings", and copy the following table of settings into the add-an-attachment page for this bug? (which is at https://bugzilla.mozilla.org/attachment.cgi?bugid=1719476&action=enter -- there's a blank area labeled "File" near the top of that page, where you can paste a bunch of text to create an attachment here)

Flags: needinfo?(trishap)

See attached
Just know this only happens the first time you try and print from Mozilla after the browser has been opened.

Flags: needinfo?(trishap)

Thanks! I'll paste your question answers (from your bugzilla.txt attachment) here, so they're visible to other folks skimming the bug report.

It's useful to know that you're using a receipt printer; we've unfortunately had a handful of bugs that affect those which have been difficult to track down. Note also that bug 1672389 seems to be filed on an issue in the same model of printer (which also dates back to Firefox 82, which as you noted is affected here as well). I'm adding that bug to "see also" since there may be some relation between them.

Quoting reporter's answers from attachment:

(1) Did this just start happening recently before you filed this bug, or has it been happening for a while?

A while even in V82

(2) What printer model are you printing to, and are you connected directly (via USB), or is it a network printer?

CITIZEN CT-S310II receipt printer connected via USB

(3) Does this happen with basic pages like https://www.example.org/ ? (good simple test page)

Yes

(4) It looks like you're using Windows 10 -- is that correct? (or maybe Windows 7?)

WINDOWS 10 pro

(5) Does it work correctly on the first try if you use "Save to PDF"?

Seems to but kind of odd due to it being a receipt and not easily put in PDF form

Keywords: regression
See Also: → 1672389
Summary: Always have to send print job twice upon opening firefox → Always have to send print job twice upon opening firefox, with Citizen CT-S310II receipt printer
Whiteboard: [old-ui+]
Attachment #9234731 - Attachment description: bugzilla.txt → answers to questions, and printer settings from about:support
Flags: needinfo?(jwatt)

Bug 1725311 sounds like it may be something similar -- the first attempt to print just fails, but then after that it works.

See Also: → 1725311
You need to log in before you can comment on or make changes to this bug.