Bug#1061599: gnome-online-accounts: cannot login to Nextcloud 26.0.7 since 3.49.0-1 - http 405 method not allowed

[Alban Browaeys]

The 405 status was locally and manually fixed by applying the "webdav
migration" implemented upstream in merge request 146.

That is in ~/.config/goa-1.0/accounts.conf for my owncloud provider,
add "remote.php/webdav" to the "https://nextcloud.domain/" in the "Uri"
key.
I also create CalDavUri and CardDavUri from the "Uri" key but appending
"remote.php/dav" to them instead of "remote.php/webdav".
I got the clue from the issue "critical when testing new WebDav support
on existing nextcloud account: g_uri_peek_scheme: assertion 'uri !=
NULL' failed"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/276 ).


The fix: "goabackend: migrate existing WebDAV
accounts"https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/146
It is merged in 3.49.1 (while Debian is 3.49.0).

Note that 3.49.1 also includes a migration to GTK4 and API changes
which would breaks gnome-control-center 45 "Bump soname?"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/291
Though we have gnome-control-center 46~alpha-2 in trixie and 46~beta-1
in sid, I don't know which gnome-control-center 46 release was ported
to this API (as I have 1:46~alpha-2 currently I believe it is not
ported yet as it works with gnome-online-accounts 3.49.0).

Might be the best way for now is to port the merge request 146 to
3.49.0 in Debian trixie.

The API breakage in gnome-control-center was done in "goabackend: port
to GTK4"
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/142
which is merged into 3.49.1.

Cheers,
Alban

On Sat, 27 Jan 2024 08:11:10 +0100 Alban Browaeys <prahal at yahoo.com>
wrote:
> Package: gnome-online-accounts
> Version: 3.49.0-1
> Severity: important
> 
> 
> I upgrade gnome-online-accounts from 3.48.0-2 to 3.49.0-1, I still
had
> Nextcloud ok in gnome-control-center (Settings) 1:46~alpha-2.
> Then on one box I rebooted, then I got "Credential have expired" for
> Nextcloud in Settings. Trying to authenticate anew gave me "Error
> connecting to WebDAV server: Authentication failed".
> 
> I then tried on the other box, which still had nextcloud login ok,
where
> I also upgraded gnome-control-center but did not yet restart it, to
> kill goa-daemon and restart it. Then I ended up with the same error
as
> wiht the box I rebooted.
> 
> Settings output is:
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting new address enumeration
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: lookup_by_name_with_flags_async: starting new lookup for
cloud.prahal.homelinux.net with GTask 0x5581b3e13eb0, LookupData
0x5581b3ce9500
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: lookup_by_name_with_flags_async: starting new lookup for
cloud.prahal.homelinux.net with GTask 0x5581b3d76160, LookupData
0x5581b3d1c5b0
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Address enumeration succeeded
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting TCP connection attempt
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: TCP connection successful
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Starting application layer connection
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]: GLib-
GIO: GSocketClient: Connection successful!
> janv. 27 07:59:10 hermes org.gnome.Settings.desktop[131923]:
GoaBackend: goa_dav_client_check(): response (0x5581b422b970, 405)
> 
> Note the 405 status.
> Could it be my old Nextcloud version does not support a method call
from
> goa 0.49.0?
>