Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

No longer able to Print Messages since updating to ver. 45

  • 1 risposta
  • 1 ha questo problema
  • 1 visualizzazione
  • Ultima risposta di Matt

more options

Problem #2 since updating to T-bird version 45:

Sometimes I like to compose a message then print a copy before sending. Prior to 45 I would do the following:

1) Click the "Write" button to start a new message. 2) Type and spell check my message. 3) Press Ctrl+P to open Print dialog box. 4) Select the printer (sometimes laser, sometimes pdf). 5) Click OK and done.

Since updating to ver. 45, I can only get to step 2. Unable to open the Print dialog box using any of the standard methods.

Is this a bug that will be fixed? Is there a work around? As I use this process many times throughout the day should I roll back to the previous version of T-bird?

thanks for your support,

Problem #2 since updating to T-bird version 45: Sometimes I like to compose a message then print a copy before sending. Prior to 45 I would do the following: 1) Click the "Write" button to start a new message. 2) Type and spell check my message. 3) Press Ctrl+P to open Print dialog box. 4) Select the printer (sometimes laser, sometimes pdf). 5) Click OK and done. Since updating to ver. 45, I can only get to step 2. Unable to open the Print dialog box using any of the standard methods. Is this a bug that will be fixed? Is there a work around? As I use this process many times throughout the day should I roll back to the previous version of T-bird? thanks for your support,

Soluzione scelta

Yes it is a bug that will be fixed, in about a week with V45.1

Leggere questa risposta nel contesto 👍 1

Tutte le risposte (1)

more options

Soluzione scelta

Yes it is a bug that will be fixed, in about a week with V45.1