Created attachment 166159 [details] Screenshot of an error likely to do with QtWebView and logging in *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Oops I submitted it by accident :(
STEPS TO REPRODUCE: 1. Click `Login` 2. Input any server URL 3. Click `Continue` OBSERVED RESULT: The app doesn't seem to do anything on the GUI, but shows this error in the terminal: ``` file:///usr/qml/org/kde/kirigami/PageRow.qml:718:5: QML StackView: push: qrc:/qt/qml/org/kde/tokodon/content/ui/LoginFlow/AuthorizationPage.qml:5 module "QtWebView" is not installed ``` EXPECTED RESULT: Tokodon shows the login screen fine and lets me log in. SOFTWARE/OS VERSIONS: Qt Version: 6.6(probably .2) KDE Frameworks Version: 6.0.0 KDE Plasma Version: Not using Plasma (GNOME 45) Flatpak: 1.15.6 Tokodon: Nightly Flatpak
Where did you source this flatpak version? Our qt6 nightly repository or did it release on Flathub without me knowing? :D
(In reply to Joshua Goins from comment #3) > Where did you source this flatpak version? Our qt6 nightly repository or did > it release on Flathub without me knowing? :D By `qt6 nightly repository`, I believe you mean this: https://cdn.kde.org/flatpak/tokodon-nightly/ ? If so, I got it from there :)
I don't know if this helps at all, but adding the env `QML_IMPORT_PATH=/app/qml/` makes Tokodon go to the Authorization page and give this error instead: `No WebView plug-in found!`
This is odd, someone mentioned this bug to me again in chat and then I tried it on my machine (F40 KDE) and the authorization worked. I wonder why it works on my machine and not others, maybe this part of Flatpak is inconsistent for some reason. Marking as confirmed as this is definitely still an issue
Closing as this is "fixed" in a way in 24.05, now live on Flathub. It restores the old pre-24.02 method and I tested it now which works. In the case that even that doesn't, we have an auth code backup.