Replying about the accountsservice part, we got some issues resolved there before the release but the bug here is a different problem then the one addressed in accountsservice 22.08.8-1ubuntu7.
The issue is in the indicator codebase and the right fix is what has been uploaded for (ayatana-)indicator-messages recently but Marco also worked on making accountsservice more robust to such coding errors. The fix has been commited upstream now but not uploaded to Ubuntu yet (we tend to use 'fix commited' on desktop component for things which have a fix available in the upstream vcs which can be slightly confusing)
@Andreas
Replying about the accountsservice part, we got some issues resolved there before the release but the bug here is a different problem then the one addressed in accountsservice 22.08.8-1ubuntu7.
The issue is in the indicator codebase and the right fix is what has been uploaded for (ayatana- )indicator- messages recently but Marco also worked on making accountsservice more robust to such coding errors. The fix has been commited upstream now but not uploaded to Ubuntu yet (we tend to use 'fix commited' on desktop component for things which have a fix available in the upstream vcs which can be slightly confusing)