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

Cannot Print on Typora #5033

Open
benji88i opened this issue Jan 28, 2022 · 28 comments
Open

Cannot Print on Typora #5033

benji88i opened this issue Jan 28, 2022 · 28 comments

Comments

@benji88i
Copy link

Hi there,

Love the app so much, using it everyday and really depend on it. I was just about to buy the licence but I have some issues.

Running version: 1.0.4 - Flathub Version

Running System - Fedora 35 (Gnome 41.3)

We cannot see our printer listed when printing. We checked flatseal permissions and it is set to CUPS allowed for printing.

image

image

Whenever we try to change anything in the print dialogue box it freezes.

As an example here is a print dialogue box for our word prompt which shows our printer listed

image

@abnerlee
Copy link
Contributor

abnerlee commented Feb 1, 2022

Does print function in the binary version https://typora.io/linux/Typora-linux-x64.tar.gz works?

@benji88i
Copy link
Author

benji88i commented Feb 2, 2022

Hi there thanks for writing,

Thank you also for this idea. I downloaded and extracted the tar file. Then I opened and ran the "Typora" file.

All worked well.

image

After this I ran tried to print again and this time to my suprise my listed printer was there this time unlike that flathub version.

I clicked the printer I wanted and then clicked "print".

Immediately after this it crashed and closed down :-(

image

Not sure what is causing it to crash, :-(

I really need to print

@abnerlee
Copy link
Contributor

abnerlee commented Feb 8, 2022

Please use workaround: Export to PDF then print, or export to HTML then print.

For both versions, does other printers (like print to file) works?

@bertradio
Copy link

bertradio commented Feb 18, 2022

Same printing problem. Running 1.1.3 binary on Linux Mint 20.3.

When trying to print, printer selection box opens, but whatever I choose (including print to file) Typora crashes -- closes with no error message. Have the same problem with Joplin and MarkText and it appears to be related to changes in Electron.

No files in ~/.config/Typora/Crash Reports. Typora.log has:

INFO 2/18/2022, 6:42:19 AM [focus] 1
INFO 2/18/2022, 6:42:30 AM load file [/tmp/1645195350483-0.5610805644576429.html] for PDF export
INFO 2/18/2022, 6:42:31 AM [blur] 1
INFO 2/18/2022, 6:42:31 AM [win] blur
INFO 2/18/2022, 6:42:34 AM [focus] 1

Export and print is a workaround, but it would be great for printing worked in Typora.

Thanks

@benji88i
Copy link
Author

hi sorry for delay, yes both versions print to file works. Its odd as I had no issues for over 1 year on Fedora. is this an issue on other Linux distros?

@benji88i
Copy link
Author

Same printing problem. Running 1.1.3 binary on Linux Mint 20.3.

When trying to print, printer selection box opens, but whatever I choose (including print to file) Typora crashes -- closes with no error message. Have the same problem with Joplin and MarkText and it appears to be related to changes in Electron.

No files in ~/.config/Typora/Crash Reports. Typora.log has:

INFO 2/18/2022, 6:42:19 AM [focus] 1 INFO 2/18/2022, 6:42:30 AM load file [/tmp/1645195350483-0.5610805644576429.html] for PDF export INFO 2/18/2022, 6:42:31 AM [blur] 1 INFO 2/18/2022, 6:42:31 AM [win] blur INFO 2/18/2022, 6:42:34 AM [focus] 1

Export and print is a workaround, but it would be great for printing worked in Typora.

Thanks

yes thats what mine does. is there another team we can get support from as they seem to have their hands full here

@bertradio
Copy link

Strange that the developer didn't notice this. It's not a small bug.

@abnerlee abnerlee changed the title Cannot Print on Typora Cannot Print on Typora [Flathub] Feb 21, 2022
@abnerlee
Copy link
Contributor

This should relates to flathub, since the binary version is working fine.

flathub/org.libreoffice.LibreOffice#90
https://discourse.flathub.org/t/printing-from-firefox-flatpak/546/7

@bertradio
Copy link

bertradio commented Feb 21, 2022

I am running the binary version 1.1.4 and the problem persists. Did try the flatpak but removed it. What binary version are you using?

@bertradio
Copy link

Just updated to version 1.1.5 and the problem persists.

@benji88i
Copy link
Author

I tried to print on the binary version and it didn't work. It did exactly the same thing. I will try again. I can't understand why the Linux guys get treated like trash all the time by developers like we are third class citizens. If this issue was on Mac osx it would be fixed within a few days, I filed this issue a month ago and nobody at typora seems to care. Does it run okay with a .Deb version. For whatever it's worth I have the same issue on other flatpaks but they don't crash like typora, just no print.

@bertradio
Copy link

I have the same issue with either the deb or flatpak versions.

@abnerlee abnerlee changed the title Cannot Print on Typora [Flathub] Cannot Print on Typora Mar 3, 2022
@benji88i
Copy link
Author

benji88i commented Mar 3, 2022

HI @bertradio acutally thats not correct, I have tested other versions on different distros and the issue persists. including the binary version. Can you suggest any checks we can do?

@bertradio
Copy link

I'm not sure what you mean by "thats not correct". I find the same printing issue with two other Markdown editors: Marktext and Jopin. I think it may be related to recent changes in Electron.

@benji88i
Copy link
Author

benji88i commented Mar 3, 2022

My apologies, I am sorry i mixed you up with someone else. abnerlee mentioned this issue does not happen on other distros or package variants, which is not true. it happens on thr source file version as well..

@abnerlee
Copy link
Contributor

Does the new dev version works (https://typora.io/releases/dev) ?

@bertradio
Copy link

No. Same problem with 1.2.2-dev.

@abnerlee
Copy link
Contributor

@bertradio Could you try launch Typora from terminal, make it crash by printing, then paste the crash message from the terminal?

@bertradio
Copy link

~ $ typora
[19968:0314/082046.465120:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
Crashing due to FD ownership violation:
#0 0x55907bbf4df3
#1 0x55907bca247c
#2 0x55907bca2441
#3 0x7f3421ba3cdb
Trace/breakpoint trap

@bertradio
Copy link

That was running 1.2.2-dev

@abnerlee
Copy link
Contributor

@bertradio Does disable GPU works? (launch Typora with parameter --disable-gpu )

@bertradio
Copy link

No.
$ typora --disable-gpu
[20486:0314/082515.158587:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
Crashing due to FD ownership violation:
#0 0x56257dcd8df3
#1 0x56257dd8647c
#2 0x56257dd86441
#3 0x7fefc5ad2cdb
Trace/breakpoint trap

@abnerlee
Copy link
Contributor

may relates electron/electron#31151

@bertradio
Copy link

I think so because I have the same issue with Joplin and Mark Text which also use Electron.

@benji88i
Copy link
Author

benji88i commented Apr 2, 2022

Hi there @abnerlee what info do you need that could help?

@moksamedia
Copy link

Same issue with Typora on PopOS 20.10. Typora crashes on print. Marktext is doing this as well.

syslog output:

Apr  4 10:34:37 pop-os kernel: [58304.172530] Typora[116987]: segfault at 138 ip 00005650c1f72b84 sp 00007fff5a9b4d90 error 4 in Typora[5650bee48000+6461000]
Apr  4 10:34:37 pop-os kernel: [58304.172569] Code: c4 08 5b 5d c3 cc 55 48 89 e5 53 50 48 89 fb 48 83 c6 08 e8 6e 8a b1 ff 48 89 d8 48 83 c4 08 5b 5d c3 cc cc cc cc 55 48 89 e5 <8b> 87 38 01 00 00 5d c3 cc cc cc cc 55 48 89 e5 8b 87 58 01 00 00

@mrdanbrooks mrdanbrooks mentioned this issue Oct 10, 2023
3 tasks
This was referenced Mar 24, 2024
@abnerlee
Copy link
Contributor

abnerlee commented Jul 1, 2024

try flathub/org.libreoffice.LibreOffice#90 (comment)
which maight work

@bertradio
Copy link

bertradio commented Jul 1, 2024 via email

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

No branches or pull requests

4 participants