While running eos-updater-ctl manually as an advanced user utility, you may encounter the following error message:
GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Fetch() while in state Ready (36)
This may appear in the context of a larger exception trace such as:
Traceback (most recent call last):
File "/usr/bin/eos-updater-ctl", line 422, in <module>
main()
File "/usr/bin/eos-updater-ctl", line 418, in main
sys.exit(args.function(**args_dict))
File "/usr/bin/eos-updater-ctl", line 222, in command_update
force=force, timeout=timeout)
File "/usr/bin/eos-updater-ctl", line 204, in command_fetch
return command_dbus('fetch', block, quiet, parameters)
File "/usr/bin/eos-updater-ctl", line 172, in command_dbus
proxy.call_sync(qualified_method_name, parameters, 0, -1, None)
gi.repository.GLib.Error: g-io-error-quark: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Fetch() while in state Ready (36)
The implication of such message is:
This is a known minor issue. In future, eos-updater-ctl may be improved to better indicate these relatively usual conditions in such cases, rather than presenting it as an error message.
If you see this error message in a context other than from a manual run of eos-updater-ctl then you should report this as a bug.