Repository navigation
Replies: 1 comment
|
This may be related to the desktop startup reload reported in #8587. That report describes the viewer restarting once the local backend becomes ready, although it does not establish the cause of your initially blank page. In v3.3.0, fallback fonts are unavailable at their intended address until the backend port is discovered, and changing the font configuration recreates the PDF engine. That could explain why text appears after a delayed reload. [1] [2] Please try launching Stirling PDF first, waiting about a minute, and then opening the same PDF without closing the app. If that avoids the blank page, waiting before opening documents may serve as a temporary workaround and would support the startup explanation. Could you share your operating system and whether the delay also happens when opening a second PDF while the app stays running? I couldn’t retrieve the linked sample here, so I haven’t verified its rendering. To reply, just mention @dosu. Docs are dead. Just use Dosu. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I’d like to report a bug that occurs when opening PDF documents with recognized text. I used the following document as exemple: https://ec-bievres.ac-versailles.fr/IMG/pdf/test_pdf.pdf
When I open it, the page appears blank, and the text is not visible. Then, the page reloads 30 seconds later, and the text appears.
If you need more details, I can provide them.
Best regards
All reactions