| Summary: | Kasts won't re-login to GPodderSync (Nextcloud) | ||
|---|---|---|---|
| Product: | [Applications] kasts | Reporter: | yamiyukisenpai |
| Component: | general | Assignee: | bart |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 24.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Snap | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-3087987-0.html | ||
|
Description
yamiyukisenpai
2025-03-08 11:27:48 UTC
Could it be that you accidentally removed the app password for Kasts in your nextcloud instance, or something similar? I'm asking because on the Kasts side you cannot get logged out. Kasts sends the password as authentication key on every single remote request. What *can* happen is that the remote side stops accepting that password/keyphrase at some moment. If that ever happens, you should be able to simply press the logout button, after which you can log back in with an updated password. Because authentication is done with every single request, the logout button simply "forgets" the current password. It doesn't really inform the remote server about you having logged out. Or was there another problem? Is there anything we can still do? Created attachment 179927 [details] attachment-3087987-0.html I’m waiting for mine to log me out On Sun, Mar 23, 2025 at 09:32, <[bugzilla_noreply@kde.org](mailto:On Sun, Mar 23, 2025 at 09:32, <<a href=)> wrote: > https://bugs.kde.org/show_bug.cgi?id=501222 > > bart@mogwai.be changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from bart@mogwai.be --- > Is there anything we can still do? > > -- > You are receiving this mail because: > You reported the bug. I'm still trying to understand your issue. If you are syncing with gpodder-nextcloud (not gpodder.net), then the logout button doesn't even go online. It simply deletes the locally stored credentials. So I don't see how this could be hanging unless the app is unable to access its local configuration files. But then that would be a completely different issue that would pop up in other places as well. Could you perhaps start the app from the command line and check for error messages in the console? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |