| Summary: | Black screen when trying to open PDF on Android 14 | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Richard <rrosner5> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aacid |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Dummy PDF from w3.org (https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf) | ||
|
Description
Richard
2023-08-08 09:35:44 UTC
Same result with png, tiff, ps; with djvu and xps/oxps I got the error that it couldn't find a plugin to handle them, even though the F-Droid page claims they are supported. Can you confirm this only happens to you with Android 14? i.e Android 13 on the same phone works? I can't confirm nor deny that, I've just learned about that F-Droid repository and have been on the beta since the first one dropped. I just assumed that if it wouldn't have worked on 13 somebody would have reported that. Also I assumed that it's unlikely to be device specific as what Google ships is more or less stock Android and if this breaks it's usually because some OEM screwed stuff up. So chances would be if it's due to a change in Android 14 it would affect other devices too when they get the update, unless it's s big that's going to be fixed until then. I've just checked out the PDF import tool of KDE Itinerary. It also shows a black screen and crashes, but afterward it does have the data from the PDF imported. So it only seems to be a problem with displaying the content, not with reading it. Also from F-Droid, v23.04.3 with Qt 5.15.10 and poppler 23.06.0 > I can't confirm nor deny that
Would need to be good to get someone to confirm if the update to Android 14 is what breaks this or not.
Maybe someone can verify by using Android Studio and its built-in set of VM images. At least that's the easiest way to test if the switch from Android 13 to 14 breaks stuff. Even though I have no idea how to tell it to boot an arm64 image instead of an x86 one (just to make sure that's no influence). I'd love to do that, but my laptop is far from powerful enough to pull that off. We fixed this last year "Cherry picked commit from Qt6 in order to fix black screen issue in Okular Android" from https://community.kde.org/GSoC/2023/StatusReports/ShivoditGill (In reply to Albert Astals Cid from comment #7) > We fixed this last year > > "Cherry picked commit from Qt6 in order to fix black screen issue in Okular > Android" from https://community.kde.org/GSoC/2023/StatusReports/ShivoditGill I can't check as I'm no longer on Android 14. But installing it fresh from the KDE F-Droid repo on 15 Beta 4.2, it is broken again. Opening the app doesn't show anything other than a blank screen, so does trying to open a PDF in it from a file manager. (In reply to Richard from comment #8) > (In reply to Albert Astals Cid from comment #7) > > We fixed this last year > > > > "Cherry picked commit from Qt6 in order to fix black screen issue in Okular > > Android" from https://community.kde.org/GSoC/2023/StatusReports/ShivoditGill > > I can't check as I'm no longer on Android 14. But installing it fresh from > the KDE F-Droid repo on 15 Beta 4.2, it is broken again. Opening the app > doesn't show anything other than a blank screen, so does trying to open a > PDF in it from a file manager. I can check next week as the Pixel 9 devices ship with 14 though. (In reply to Richard from comment #9) > (In reply to Richard from comment #8) > > (In reply to Albert Astals Cid from comment #7) > > > We fixed this last year > > > > > > "Cherry picked commit from Qt6 in order to fix black screen issue in Okular > > > Android" from https://community.kde.org/GSoC/2023/StatusReports/ShivoditGill > > > > I can't check as I'm no longer on Android 14. But installing it fresh from > > the KDE F-Droid repo on 15 Beta 4.2, it is broken again. Opening the app > > doesn't show anything other than a blank screen, so does trying to open a > > PDF in it from a file manager. > > I can check next week as the Pixel 9 devices ship with 14 though. Just tested on Pixel 9 and Pixel Tablet on Android 14, same result on both. So whatever you fixed, it wasn't enough. Which build are you testing? Whatever was the latest in the KDE F-Droid repo. As no part of the app is accessible, I couldn't even go to the About Okular screen. From what I can tell from the page in F-Droid it's still 1.3.0 added on 02/10/24, so it must be newer than what I used a year ago, but it has the same version number. 1.3 is mega old, please try unstable 24.11.70 from https://cdn.kde.org/android/nightly/fdroid/repo/ Yes, that one is working. It's far from perfect but at least it can display PDF files. |