Crash when try to print (linux, typora 1.9.3)

[profhccaesar]

• 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
After clicking menu item "file -> print" or pressing alt+shift+p, typora crashes with following output:

[1075244:0104/144047.252134:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
Crashing due to FD ownership violation:
#0 0x5586a2852a33 <unknown>
#1 0x5586a284ab3c <unknown>
#2 0x5586a284aaf7 close
#3 0x7ff9e881aef3 <unknown>
Trace/Breakpoint ausgelöst

Sometimes the system's print dialog flashes briefly but then disappears again immediately.

To Reproduce
Steps to reproduce the behavior:

1. Start Typora
2. Optional: open any markdown file
3. Press Alt+Shift+P or execute menu item "File -> Print"
4. See error

Expected behavior
Opening system print dialog to perform printing.

Screenshots / Screencasts
https://github.com/user-attachments/assets/7ccfb5d1-75e3-4b34-a522-f7a55f1b0f32

Sample Markdown File
Optional - crash occurs also without a file or with any file. Use following as sample:

Hello world!

Desktop (please complete the following information):

• OS: Linux Mint 21.1 "Vera" x84-64 (based on Ubuntu 22.04 LTS "Jammy")
• Desktop Environment: Cinnamon 5.6.8

Typora Version

• 1.9.3-1 amd64
• Installed per package manager "apt"

Additional context
None.

[profhccaesar]

Added output of strace:

$ strace typora

typora-crash-on-print-strace.log

[shujiejune]

I met similar crash as stated in #6208 , hope the developer could notice this issue asap...

[abnerlee]

relates electron/electron#31151

[shujiejune]

Does that mean it's not likely to fix this issue github.com/typora/typora-issues/issues/6208 <#6208> as an end-user? Since the fix is using child_proc.fork() in Node.js Jan 8, 2025, 20:27 by ***@***.***:

…

relates > electron/electron#31151 <electron/electron#31151> — Reply to this email directly, > view it on GitHub <#6209 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/BAZVM77G4JU3TC5DHLMQW3T2JX3EZAVCNFSM6AAAAABUTEGPFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZZGE2TONJZGE>> . You are receiving this because you commented.> Message ID: > <typora/typora-issues/issues/6209/2579157591> @> github> .> com>

[LanceHaverkamp]

Same here, I'm a brand-new (trial) user. Installed on OpenSUSE Leap (current 15.6) KDE Plasma desktop.
100% of the time, it crashes when I try to print. My printer is a Lexmark B2236DW monochrome laser, connected through the LAN.

However, when I try to PRINT a pdf file (rather than export), I get the following:
** (typora:4294): WARNING **: 18:41:22.417: failed to get find a colord device: The name org.freedesktop.ColorManager was not provided by any .service files

** (typora:4294): WARNING **: 18:41:27.400: GDBus.Error:org.freedesktop.Avahi.TimeoutError: Timeout reached

** (typora:4294): WARNING **: 18:41:27.400: GDBus.Error:org.freedesktop.Avahi.TimeoutError: Timeout reached
Segmentation fault (core dumped)

Possibly unrelated: I'm getting the following message in the terminal, at launch:
WARNING: radv is not a conformant Vulkan implementation, testing use only.