Skip to content
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

Error when trying to export to PDF (Linux snap, v 2.7.14) #18

Open
MWH-Rookie opened this issue Apr 7, 2022 · 2 comments
Open

Error when trying to export to PDF (Linux snap, v 2.7.14) #18

MWH-Rookie opened this issue Apr 7, 2022 · 2 comments

Comments

@MWH-Rookie
Copy link

Hi

When I try to export a notebook to PDF (after fresh snap install of joplin desktop and just taking my first notes), I first get a file browser window, which lets me choose a destination of the PDF and afterwards I get an error message.
This message states:
"Error: ENOENT: no such file or directory, stat '/home/myname/snap/joplin-desktop/27/.config/joplin-desktop/tmp/VERYLONGALPHANUMERICFILENAME.html"
Well, and that's it.

Environment

Joplin version: 2.7.14
Platform: Linux
OS specifics: Ubuntu 20.04

Steps to reproduce

see above

Describe what you expected to happen

I expected a PDF to be created.

I have issued this bug first at laurent22/joplin#6372 and was directed here.

@JGCarroll
Copy link
Owner

Thanks for the information, I'll try schedule some time later to take a look at this on my end.

In the meantime, can you please try activate the Joplin debugging tools and send over the log files it produces?
https://joplinapp.org/debugging/

It's interesting to me that the error message specifies ".html", rather than ".pdf". I wouldn't expect there to be an HTML file there either if you're using a PDF export. It might be that a .pdf is actually being generated properly but not opened because of the incorrect filename. If you open /home/myname/snap/joplin-desktop/27/.config/joplin-desktop/tmp/ after attemting to export the PDF, is the export actually in there at all?

@JGCarroll
Copy link
Owner

Hello again,

I'm struggling to reproduce this on my end on a fresh set-up. I've tried entering a myraid of perculiar filenames incase that has anything to do with it, although it doesn't appear to make much of a difference.

Unfortunately, it looks like I'd definitely need the logs in order to have a good chance of working out what might be going on in this instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants