https://bugs.kde.org/show_bug.cgi?id=473138
--- Comment #6 from Richard ---
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
https://bugs.kde.org/show_bug.cgi?id=473138
Albert Astals Cid changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=473138
--- Comment #4 from Richard ---
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
https://bugs.kde.org/show_bug.cgi?id=473138
--- Comment #3 from Richard ---
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
https://bugs.kde.org/show_bug.cgi?id=473138
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=473138
--- Comment #1 from Richard ---
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.
--
You are receiving this mail because:
You
