搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Cannot access Printer Properties

  • 4 个回答
  • 2 人有此问题
  • 3 次查看
  • 最后回复者为 cor-el

more options

I have quite a few users who are having a problem when they try to print from FF 22.0. When they try to print a webpage, email, document, etc. and go into the Properties for the printer to change it from Letter to Legal, or Legal to Letter, the item will not print. I've reset the printer in about:config and that didn't help. If I go into the prefs.js and remove the printers, close FF and reopen that helped, however the next day, I get another call from the users w/ the same issue. Is there a fix, or workaround? I don't really have time to edit the prefs.js file every day for 100+ employees.

Thank You for any help.

I have quite a few users who are having a problem when they try to print from FF 22.0. When they try to print a webpage, email, document, etc. and go into the Properties for the printer to change it from Letter to Legal, or Legal to Letter, the item will not print. I've reset the printer in about:config and that didn't help. If I go into the prefs.js and remove the printers, close FF and reopen that helped, however the next day, I get another call from the users w/ the same issue. Is there a fix, or workaround? I don't really have time to edit the prefs.js file every day for 100+ employees. Thank You for any help.

所有回复 (4)

more options

Are you using a an add-on that may be messing with Printer Preferences?

more options

Nothing I can see. This is on a Citrix environment as well, so all users are using the same version of FF and same plug-ins, but not all users seem to be affected. I'm looking at printer drivers to see if there could be something there.

more options

I wonder whether a user.js file could help, by overriding the user.js printer settings with "known good" settings at startup. I don't know whether a user.js file can reset a preference.

more options

Do you know which line(s) in prefs.js are causing this problem (i.e. do all files have the same problematic lines)?

Did you try to delete all prefs.js and possible numbered prefs-##.js files?