Closed Bug 1243919 Opened 8 years ago Closed 5 years ago

I am unable to print to a dymo 450 printer using FireFox after the last update on Jan. 26th

Categories

(Core :: Printing: Output, defect)

44 Branch
Unspecified
Windows 10
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: vern, Unassigned, NeedInfo)

Details

(Keywords: regressionwindow-wanted)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160123151951

Steps to reproduce:

I tried to print to my dymo 450 printer using an application that is used with firefox.  The application ran fine on Monday, but did not work on Tuesday.


Actual results:

When sending the print request to the printer nothing happens.  But if I send a test to the dymo directly from the computer the dymo tests fine.


Expected results:

The dymo should have printed a prescription label. It did not.
Severity: normal → major
OS: Unspecified → Windows 10
Did you make a test with a fresh profile?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

If that doesn't change anything, there is a possible regression in FF44.

1) Test Nightly, maybe it's already fixed: https://nightly.mozilla.org/ (you can use a custom profile not necessarily your current profile)
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

2) As you're able to reproduce the issue on your side, could you install Mozregression to find a regression range.
See http://mozilla.github.io/mozregression/ for the details (it's python 2.7 package)
Use the command-line version and run the command "mozregression --bits=32 --good=43" and try to reproduce the issue for each nightly downloaded by Mozreg.
At the end, copy here the pushlog provided in the console output.
Flags: needinfo?(vern)

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.