Joplin 2.5.8 (and later) Crashes when Printing

[dfwdraco76]

This morning I upgraded to 2.5.8. I tried to print something, and as soon as I clicked the print button on the dialogue, Joplin crashed. Now when I reopen Joplin, just opening the print dialog triggers a crash.

Environment

Joplin 2.5.8 (prod, linux)

Client ID: -- Sync Version: 3 Profile Version: 39 Keychain Supported: No Revision: dbdb82d

Linux Mint 20.2 x86_64

Steps to reproduce

1. Go to File, select Print

Describe what you expected to happen

Normal print behavior

Logfile

If anything was displayed in the console, I couldn't see since the application crashes. Trying to attach log.txt but it's saying "is not included in the list"

[dfwdraco76]

Here is a link to the log.txt file: https://mega.nz/file/3bJ0SRbT#BfRuBQtV1vGELq2q56wvF6FZ5vpfbR3T90qoXeocUqY

[laurent22]

Well I'm not going to download a 174 MB log. Could you copy and paste the relevant lines here please? (probably the last lines from your log)

[laurent22]

Probable upstream bug: https://github.com/electron/electron/issues/31151

[dfwdraco76]

Sorry, just followed the instructions. The log really doesn't show much, I just reproduced it and have this in the log

2021-10-31 17:23:43: "SearchEngine: Updated FTS table in 1ms. Inserted: 0. Deleted: 0"
2021-10-31 17:23:43: "CommandService::execute:", "print", "[]"
2021-10-31 17:23:43: "DecryptionWorker: starting decryption..."
2021-10-31 17:23:43: "DecryptionWorker: completed decryption."

I should add that bug doesn't sound right; I actually have 2 printers installed.

[laurent22]

Could try to you start the .AppImage directly from the command line? Then when it creates it might print an error directly in the console

[dfwdraco76]

dfwdraco76@ncc-1701:~/Applications$ ./Joplin_56d10c0053a5732ac65b421a6685c360.AppImage
qt5ct: using qt5ct plugin
AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)
xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(Use `@joplinapp-desktop --trace-warnings ...` to show where the warning was created)
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:81552) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
Crashing due to FD ownership violation:
#0 0x563799b76f83 <unknown>
#1 0x563799c1dfbc <unknown>
#2 0x563799c1df81 close
#3 0x7f926c87bcdb <unknown>
Sun 31 Oct 2021 05:51:41 PM CDT

[laurent22]

Yes it's the same bug as the upstream one. It's probably not related to not having any printer, but something else. Pretty much every new Electron version brings new bugs and crashes related to printing unfortunately. In the meantime you can export to PDF and print that file, although it's obviously not as convenient.

[dfwdraco76]

I just upgraded to 2.5.10 and the same thing happens when I try to print. I'd thought about the print to PDF functionality as a workaround too, but the dialog disappears and the app crashes before I can change the printer to "print to file". Looks like the crash info is the same:

Crashing due to FD ownership violation:
#0 0x5561ffd1af83 <unknown>
#1 0x5561ffdc1fbc <unknown>
#2 0x5561ffdc1f81 close
#3 0x7f4c65855cdb <unknown>

[laurent22]

You get a crash when exporting PDF even with 2.5.10? Could you double-check the version in the About dialog?

[dfwdraco76]

Joplin 2.5.10 (prod, linux)

Client ID: ---
Sync Version: 3
Profile Version: 39
Keychain Supported: No

Revision: b80242d

I click File, then Print, and less than 1 second after the dialog box opens, Joplin crashes. So I cannot change which physical printer or print to file option.

I see now I can right-click a note and export it to PDF - that's probably what you were referring to. That works without issue, sorry for the misunderstanding.

[laurent22]

Ah ok, at least the pdf export bug is fixed :-) For the print one I'm not sure what can be done unfortunately. It's clearly low priority for the Electron team to get print working properly.

[philip-n]

No new information, just a "me too" post unfortunately. Just encountered the bug on Ubuntu 20.04.3 with Joplin AppImage 2.5.1, same output:

(...) (node:15470) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15. See https://github.com/electron/electron/issues/28511 for more information. Crashing due to FD ownership violation:

0 0x55af0a4a9f83

1 0x55af0a550fbc

2 0x55af0a550f81 close

3 0x7f87bc9b1cdb

Proposal Would it be feasible to simply remove the "print" command from the menu bar for the time being?

Reasons:

• If the print functionality is broken anyways, I currently see no benefit in displaying the command
• An app crash on using "basic" commands from the menu bar IMHO is quite unexpected and does not improve the trust in the app itself (no matter in which component the bug originated)

[mseliger]

Same problem here with Ubuntu Mate 21.10 and with Joplin AppImage 2.7.6 and 2.7.12. You can see that the print dialogue is comming up - then everything crashes (print dialogue and Joplin). Export to pdf and other formats works.

[bertradio]

Same problem for me with Linux Mint 20.3. And a similar thing happens trying to print markdown from both Typora and MarkText. Seems like it has to do with rendering the markdown for printing.

[mcmxcdev]

I cannot reproduce this on Manjaro Linux with Gnome 42.1

I received a Could not print: no valid printers available popup which seems to be the expected behavior. Not sure about the behavior with printers connected though.

[The-Compiler]

Looks like the behavior perhaps changed slightly, but is not fixed: I can now select a printer and print successfully, but then Joplin crashes.

[taw00]

Still a problem. Maybe gray-out the print option in Release versions of Joplin on Linux?

[benbaker76]

I was successfully printing to pdf until I made a network printer available and then it would crash as soon as I selected File->Print. I can use right-click and Export->PDF menu to get around it.

Crashing due to FD ownership violation:
#0 0x562fead2c923 <unknown>
#1 0x562feadd895c <unknown>
#2 0x562feadd8921 <unknown>
#3 0x7f1ba281def3 <unknown>
Killed

Joplin 2.9.4 / Ubuntu 22.04.1 LTS

[philip-n]

Can confirm that I also have a network printer. Same behavior as described in posts above. Joplin 2.8.8 on Ubuntu 22.04.1 LTS.

---

After clicking File > Print, there is a short pause, then the OS print dialog is visible for a split-second, then Joplin crashes.

Crashing due to FD ownership violation:
#0 0x558c05fbcf83 <unknown>
#1 0x558c06063fbc <unknown>
#2 0x558c06063f81 close
#3 0x7efdf5057ef3 <unknown>

[philip-n]

Can we rename this issue to "Latest Joplin crashes when opening print dialog on Linux" or something similar? Current title is a bit misleading, as it explicitly mentions 2.5.8.

@laurent22

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[bertradio]

The print issue continues. No idea what it is, but it is not fixed.

Thanks for the followup.

On Sat, Nov 19, 2022, at 08:02, github-actions[bot] wrote:

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum https://discourse.joplinapp.org/. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/laurent22/joplin/issues/5651#issuecomment-1320914553, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRMQALXP4H25LWWZAVDWJD22RANCNFSM5HCJIWHQ. You are receiving this because you commented.Message ID: @.***>

[dfwdraco76]

Confirmed it's still crashing for me as well.

[MSOlsen65]

Still a problem in :

" Joplin 2.8.8 (prod, linux)

Client ID: fa3bd10cfd7a4c81bec984d45551334c Sync Version: 3 Profile Version: 41 Keychain Supported: No

Revision: c2a6a13"

Running openSuse Tumbleweed fully updated.

Program crashes as soon as I click in the print dialogue. It does this regardless of printing option chosen (direct printer, network printer of print to file).

Program will export to PDF, but does not "print" to same when told to "Print to file" through the print dialogue.

This has been a longstanding problem going back at least to version 1.7.0. As such, the issue suggests that actual customer/user support is virtually non-existent. The only answer provided it that the issue lies with a third party.

Unfortunately, research into the third party shows that the only program having these issues is Joplin. Given the third party is actively used in over 30 other industrial programs, none of which have this crashing when printing problem, the only reasonable conclusion is that the issues lies within the way Joplin developers have chosen to implement the "Print" functionality.

[benintech]

It seems it's an Electron bug, not a a Joplin one. See https://discourse.joplinapp.org/t/print-does-not-work/23802/4 :

I think the problem is definitely related to Electron since I have it with Typora and MarkText as well. For me the workaround is to export to PDF and print that.

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[bertradio]

The problem remains.

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[bertradio]

The problem is still there in 2.10.3

[github-actions[bot]]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions[bot]]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

[devbrones]

2.9.17 still has the same issue, am on windows

[jonasvp]

I can confirm that 2.9.17 has the same issue on Linux. It crashes directly after selecting "Print" from menu.

Output from dmesg says:

traps: @joplinapp-desk[618570] trap int3 ip:558bf1022c25 sp:7ffc87f6c510 error:0 in @joplinapp-desktop[558bede5b000+6c46000]

[jonasvp]

I just noticed that 2.9.17 is out-of-date so I installed 2.10.18: same issue. When printing it outputs this (when starting from command line):

Crashing due to FD ownership violation:
#0 0x55b60cdc8573 <unknown>
#1 0x55b60ce738dc <unknown>
#2 0x55b60ce738a1 <unknown>
#3 0x7f5c4b118ef3 <unknown>

[dawaldow]

2.10.19 ... same issue. The good news is that the workaround is still working (export to PDF, print from PDF).