Open Bug 859930 Opened 12 years ago Updated 2 years ago

I am trying to print from SeaMonkey 2.17 and blank pages are coming out of the printer. I updated to 2.18 and still the same problem. If I print more than one page, only one page comes out and it is blank.

Categories

(Core :: Printing: Output, defect)

21 Branch
x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: citymadedotcom, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:21.0) Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build ID: 20130403022820 Steps to reproduce: I pressed print in the top toolbar, I tried pressing the commands ctrl + P, I tried pressing the print button that was on the webpage. I even tried highlighting what I needed to print, still nothing. Actual results: No matter how many pages I selected to print, one blank page came out of the printer for each attempt. Expected results: It should have printed what was on the screen. It prints fine from Google Chrome.
Severity: normal → major
Severity: major → normal
Component: General → Printing: Output
Product: SeaMonkey → Core
Version: SeaMonkey 2.18 Branch → 21 Branch
Hello, Several of our users (3 that I know of and possibly a 4th) were having this same issue. Steps to reproduce: Install Latest Firefox. Open Firefox. The printing works. Then close Firefox. Reopen it and try to print. With any printer (Including the Microsoft print to pdf printer) the printer spits out one blank page and an error dialog appears: "An error occurred while printing." Close Firefox. Rename Firefox app-data folder. Open Firefox. Firefox makes a new app-data folder. Printing works as expected. Close Firefox. Open Firefox. This second time (And every time after this) Firefox prints blank pages. Therefore, I think that the issue is something in the app-data folder. Notes: - Printing works in everything else (Word, Chrome, IE, etc.) - The previous version of Firefox (I think it was 29 or something) doesn't seem to have this issue. I've downgraded for 2 users and recommended that they use Chrome for security reasons. The third user I'm going to recommend that they use Chrome and won't downgrade in case you have tests/reports you would like me to run.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.