SUMMARY *** 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 0. Install Gpodder on Nextcloud instance (https://apps.nextcloud.com/apps/gpoddersync) from apps 1. Install Kasts from flatpak 2. Open Kasts -> Settings -> Synchronization 3. click "Login" -> Gpodder Necxtcloud 4. Fill username, password (generated for app), url (like https://example.com/apps/gpoddersync) 5. click OK OBSERVED RESULT Window with credentials closes See "Current Status: Syncing Disabled" See "Logout", "Sync Now", "Force Sync Now" buttons disabled And dont see any errors in logs (Settings -> General -> Errors) EXPECTED RESULT Syncing SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION
Did you use the url with "/apps/gpoddersync" added to the end? You just need to fill in the hostname and possibly the directory in which nextcloud is installed. The app will add the "/apps/gpoddersync" to the end to the URL internally. If that was not the problem, could you please post the debug output you get by running the app with the following command? (You can redact the output for sensitive information if you want.) The command is: QT_LOGGING_RULES=org.kde.kasts.sync=true flatpak run org.kde.kasts
(In reply to bart from comment #1) > Did you use the url with "/apps/gpoddersync" added to the end? > You just need to fill in the hostname and possibly the directory in which > nextcloud is installed. The app will add the "/apps/gpoddersync" to the end > to the URL internally. > > If that was not the problem, could you please post the debug output you get > by running the app with the following command? (You can redact the output > for sensitive information if you want.) > The command is: > QT_LOGGING_RULES=org.kde.kasts.sync=true flatpak run org.kde.kasts changing to pure domain name (the way i usually login to my cloud) did not help. Here is the output: QT_LOGGING_RULES=org.kde.kasts.sync=true flatpak run org.kde.kasts ✔ 6s Database version 6 qrc:/main.qml:326:5: QML ErrorListOverlay: Binding loop detected for property "implicitHeight" qrc:/main.qml:326:5: QML ErrorListOverlay: Binding loop detected for property "implicitHeight" qrc:/HeaderBar.qml:250:5: QML Dialog: Binding loop detected for property "implicitHeight" qrc:/HeaderBar.qml:250:5: QML Dialog: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:125:9: QML ListView: Binding loop detected for property "topMargin" file:///usr/lib/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:35:5: Unable to assign SettingsPage_QMLTYPE_282 to Page_QMLTYPE_122 file:///usr/lib/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:35:5: Unable to assign SettingsPage_QMLTYPE_282 to Page_QMLTYPE_122 qrc:/GeneralSettingsPage.qml:137:9: QML ErrorListOverlay: Binding loop detected for property "implicitHeight" qrc:/GeneralSettingsPage.qml:137:9: QML ErrorListOverlay: Binding loop detected for property "implicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/Dialog.qml:304:9: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:176:13: QML Binding: Binding loop detected for property "value" qrc:/SynchronizationSettingsPage.qml:45:9: QML Dialog: Binding loop detected for property "implicitHeight" qrc:/SynchronizationSettingsPage.qml:91:9: QML Dialog: Binding loop detected for property "y" org.kde.kasts.sync: Save the password to the keychain for "...here_was_my_username" ...no output after I gave credentials and clicked OK
After further investigation, I'm quite convinced that this is a duplicate of 451836. It seems that libsecret, which is used as backend for password storage, is completely broken since version 20. They tried to add support for local storage in flatpaks in that version, but instead completely broke it for at least the gnome-keyring backend and potentially others. So the problem is that the app tries to store the password, but that never happens because of libsecret bugs, so Kasts keeps waiting forever for the confirmation that the password has been stored.
The issue should now be solved with the latest flathub package update. (At least, it solved it for me.) Could you please check and report back?
Waiting on confirmation whether the issue is solved by latest flatpak release.
(In reply to bart from comment #5) > Waiting on confirmation whether the issue is solved by latest flatpak > release. Yes, it is now fixed! Great!
Thanks for the feedback! Glad to hear that it's solved now.