https://bugs.kde.org/show_bug.cgi?id=513775

Allen Winter <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/pim/
                   |                            |kdepim-runtime/-/commit/004
                   |                            |3b8a843b1a5946f09dc602abf13
                   |                            |1df8023b96
             Status|REPORTED                    |RESOLVED

--- Comment #6 from Allen Winter <[email protected]> ---
Git commit 0043b8a843b1a5946f09dc602abf131df8023b96 by Allen Winter, on behalf
of Christoph Ritzer.
Committed on 02/11/2026 at 22:33.
Pushed by winterz into branch 'master'.

etesync: fix account not being saved properly after setup

After setting up an EteSync account, the resource fails with "Could not get
etebase account from cache".

- Save the account from the setup wizard, and only close the wizard once saving
has finished. Previously the config dialog was destroyed before the
asynchronous keychain write completed, so the account was never saved. Errors
now show in the wizard instead of being dropped.
- Store the cache encryption key per resource instance instead of per username.
Several resources for the same user used to overwrite each other's key.
Existing entries are migrated automatically.
- Check the account only after the config reload has finished loading it.
Previously a new resource was always set offline right after setup.

M  +42   -4    resources/etesync/etesyncclientstate.cpp
M  +4    -0    resources/etesync/etesyncclientstate.h
M  +0    -1    resources/etesync/etesyncconfig.cpp
M  +15   -10   resources/etesync/etesyncresource.cpp
M  +33   -6    resources/etesync/setupwizard.cpp
M  +6    -0    resources/etesync/setupwizard.h

https://invent.kde.org/pim/kdepim-runtime/-/commit/0043b8a843b1a5946f09dc602abf131df8023b96

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to