-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on Print #203
Comments
Another issue: the built-in (protonmail) print preview dialog cannot be closed when clicking on close or the close button (nothing happens). |
@electron is known to have severe issues with printing, some recent issues:
I keep track of those upstream issues. Besides going to debug the case one day in order to find a workaround. |
The workaround, for now, is to export the email message to EML file, import it to an email client like Thunderbird and print it there. |
Electron team is making some progress on the issue. Looks like they are going to completely resolve it soon. |
Print to PDF works fine on my MacBook (Catalina, 10.15.2). (ProtonMail 4.0 beta Web UI) |
@BBaoVanC does print work for you if you call it 2+ times one by one? There was an issue that printing worked only first time and then if you call it again nothing happened. They fixed it just recently in https://github.com/electron/electron/releases/tag/v7.1.11 |
Yes, it works. Tested 4 times in a row. |
Thanks for testing the stuff. You were somewhat lucky getting it to work before it got officially fixed in https://github.com/electron/electron/releases/tag/v7.1.11 😄 It's a good thing but I'm still going to keep the issue open until the app updates to Electron v7.1.11+. |
Closing the issue as Electron has finally sorted the problem out. |
Printing a mail from ProtonMail webclient causes the entire app to crash when clicking on printing after the print preview dialog. The saved PDF file is still saved entirely on disk, so it looks like it crashes after successful printing.
The log files shows no related entry to this. Tested on Ubuntu and macOS.
The text was updated successfully, but these errors were encountered: