-
Notifications
You must be signed in to change notification settings - Fork 56
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
Typora v1.7.5 Freezes or Produce PDF with Wrong Footer are Footer is Turned On in PDF Export Setting on macOS Ventura #5846
Comments
Can confirm Linux doesn't have this problem. |
Today, I tested the latest Typora version 1.7.6 on my newly installed macOS Sonoma 14.1.1 (which is a completely fresh installation by wiping out everything on the hard drive including both OS and all app/user data) and this same problem persists. Now I can confirm this is a real bug of Typora on Mac. |
I cannot reproduce this in 1.8.2-dev (https://typora.io/releases/dev), could you check if it is already fixed in 1.8.2-dev? |
I just tried the version 1.8.2-d-ev on macOS Sonoma 14.2.1:
|
Is there any error/warning message or popups? |
There is any error/warning messages either when the lollipop mouse pointer kept spinning without exporting anything or the program exported a PDF file with a footer with the text "Footer" I just observed another bug of the latest version 1.8.7 on Debian/Ubuntu-based Linux system: PDF export function plainly stopped working (regardless of header/footer are set) with an error message: "Failed to export as PDF: undefined". Before updating, all previous versions of Typora work fine with PDF export. Furthermore, I tested the Flatpak version v1.8.6 for PDF export and surprisingly it works out smoothly. Based this overvation, my guess is that the Deb package of Linux version might use some external libraries to generate PDF, but however the latest versions have some compatibility issue with those external libraries. So, please fix the PDF export bug in Linux deb package and also the Mac version. Many thanks! |
More info regarding the PDF export problem in Debian/Ubuntu-based Linux: when I run Typora from command line and, as soon as I select Export to PDF in menu, the following error message was printed: [25404:0125/224421.343038:ERROR:platform_shared_memory_region_posix.cc(214)] Creating shared memory in /dev/shm/.org.chromium.Chromium.0RYXNK failed: No such file or directory (2) However, I checked out the permission of /dev/shm and it looks totally fine: drwxrwxrwt 2 root root 40 Jan 25 22:46 /dev/shm/ Other programs, like PostgreSQL, have no problem in creating files in this directory. Plus, I rebooted my Linux box after installing Typora, but it didn't help. |
Updates:
|
Possible to attach a screencast for us to use since we cannot reproduce this issue on our mac? |
When I turned on both header and footer options in PDF Export settings, I ended up with a PDF document with the "footer" text in both header and footer areas. |
Searched existing issues to avoid creating duplicates.
Confirmed that it can be reproduced in built-in themes without customized css.
If it only exists in 3rd party themes or css, you can still report it, but please attach the theme target or the css file. We may not "fix" it, if it is caused by 3rd party themes or css styles that we cannot support.
Searched http://support.typora.io/
Describe the bug
Typora became unresponsive when exporting to PDF file with header/footer are turned on using internal theme.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Typora should produce a PDF document with correct page footer as expected.
Screenshots / Screencasts
A screenshot of PDF export setting dialog
Sample Markdown File
Diagrams.md
Diagrams.pdf
Desktop (please complete the following information):
Typora Version
1.7.5
Additional context
[Diagrams.pdf](https://github.com/typora/typora-issues/files/12704013/Diagrams.pdf) [Diagrams.md](https://github.com/typora/typora-issues/files/12704014/Diagrams.md)Interesting, Typora v1.7.5 on Linux doesn't have this problem.
The text was updated successfully, but these errors were encountered: