-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
500 on /pages endpoint with PDFs on Linux Mint #1834
Comments
Do you have X11 installed, or only Wayland ? Java does not work on Wayland yet. |
Yes, I have X11 installed. Maybe good to mention it's Cinnamon Mint |
The error shown does not seem to have anything to do with PDF viewing. Could you provide a full logfile ? |
Sure I restarted Komga and did a few actions to fill up the logs. I did notice something from the logs when running Komga from the terminal, but couldn´t find it in the actual log file strangely enough:
I'm not sure how to enable debug logging as the documentation only mentions the jar and dockers options for that (and I don´t have the tray icon due to the other Mint issue) |
The logs don't show anything abnormal, except the X11 error. Can you try to run the jar and see if you have the same error with the PDF, so we can rule out the X11 error as noise ? |
So, the bit that I pasted into the comment is unrelated? Since that does mention some PDF renderer.
Just tried this. Interestingly, the jar works just fine. |
Alright, I did some more troubleshooting and started reinstalling, removing and installing again, clean installing. At first I thought the bug seemed to be happening from 1.15.0 onwards because 1.14.1 still worked and all the others didn´t. However, while doing this I realised that for the newer versions, I was using the workaround described in #1799, since there was no other way of starting Komga Desktop from 1.15.0 onwards. But I was still starting 1.14.1 like how youŕe supposed to start the desktop application, since that one is unaffected by #1799. So when I realised I wasn´t doing a like-for-like scenario, I used the same command in the #1799 workaround and then got the error again.
I guess this wasn´t true then or something? I did get errors on the older version, but it must've been something else then... Or I was somehow running a version higher than 1.14.1 after all... Not sure. If the workaround is indeed the cause, I think I'll use 1.14.1 until #1799 is resolved. |
@DRWAUN the log file you posted does not contain the snippet in your comment, so i overlooked the snippet. |
So it seems the PDFRenderer is tied to the display somehow (i don't know the specifics of the PDFBox library). As snd mentioned in #1799 (comment) the issue seems to lie with Linux Mint, not with Komga. There won't be any resolution to #1799 from Komga's end, so you could end up waiting a long time. I would suggest you use Docker or Jar instead. |
Alright. Thanks for looking into it. I'll close this issue |
Steps to reproduce
Expected behavior
Book loads
Actual behavior
500 on the
/pages/
endpoints with the book not loading and the console message: Could not initialize class java.awt.GraphicsEnvironment$LocalGE.Logs
Komga version
1.18.0
Operating system
Linux Mint 21.3
Installation method
from download.komga.org
Other details
I noticed this yesterday when I was still running an older version of Komga. I don´t know which one, but at least it was one that still launched like usual, so before 1.15.0 I suppose (see #1799 ). It seems to only happen to PDFs. cbz, epub and zip files don´t seem to be affected.
I had hoped that updating to the latest Komga version would fix it, but it seems not (and it introduced a new issue). It's strange, because it feels like it worked and then it didn´t anymore. I wouldn´t be surprised if Linux borked something, but I have no idea what it would be.
I used the workaround mentioned in #1799 to get 1.18.0 running.
Acknowledgements
The text was updated successfully, but these errors were encountered: