Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

I have become unable to print from a webpage

  • 1 baphendule
  • 7 zinale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu gromit01904

cottnpickr
cottnpickr
more options

I have used Firefox for several years w/no major probs. Recently, however, I cannot print from a web page on my Lexmark 7675. I can print saved documents. When I click "print preview" the screen just shows up as gray all over. If I click "print", I get a message that "an unknown error occurred while printing". I can use IE 8 and it prints fine (and "print preview" shows correctly).

What can be causing this, and what is the fix?

Thanks.

I have used Firefox for several years w/no major probs. Recently, however, I cannot print from a web page on my Lexmark 7675. I can print saved documents. When I click "print preview" the screen just shows up as gray all over. If I click "print", I get a message that "an unknown error occurred while printing". I can use IE 8 and it prints fine (and "print preview" shows correctly). What can be causing this, and what is the fix? Thanks.

All Replies (1)

gromit01904
gromit01904
more options

Same here, Windows 7 64-bit system, Firefox was at 3.6.13. Can print to the printer outside of FF with any app, not just inside FF. Also, uninstalled and reinstalled (removing all FF files in the process); tried the About:Config print.print...setting changes recommendations; tried using FF in Safe Mode as well. The about:config worked until the system was restared, then back to the same old problem. Nnothing seems to work. Ended up putting on Chrome to be able to print (didn't want to use IE). Want FF back to working! This has been a problem for the last month. Perhaps it's a Windows updated that boinked it? Oh, also updated it last night to 3.6.14 and the problem still exists.