summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update Bulgarian translationHEADmasterAlexander Shopov2023-04-071-52/+0
|
* Update Bulgarian translationAlexander Shopov2023-03-311-1/+1
|
* Update Dutch translationNathan Follens2023-03-261-262/+235
|
* Post-branch version bump to 3.49.0Emmanuele Bassi2023-03-171-1/+1
|
* Post-release version bump to 3.48.1gnome-44Emmanuele Bassi2023-03-171-1/+1
|
* Release gnome-online-accounts 3.48.03.48.0Emmanuele Bassi2023-03-172-1/+6
|
* Merge branch 'revert-c34e7f9e' into 'master'Michael Catanzaro2023-03-141-57/+31
|\ | | | | | | | | Revert "Merge branch 'wip/rishi/kcm-notification' into 'master'" See merge request GNOME/gnome-online-accounts!123
| * Revert "Merge branch 'wip/rishi/kcm-notification' into 'master'"Emmanuele Bassi2023-03-141-57/+31
|/ | | This reverts merge request !61
* Update French translationGuillaume Bernard2023-03-141-260/+240
|
* Update Catalan translationJordi Mas i Hernandez2023-03-131-369/+184
|
* Update Swedish translationAnders Jonsson2023-03-061-260/+230
|
* Update Turkish translationSabri Ünal2023-03-061-16/+16
|
* Update Polish translationPiotr Drąg2023-03-051-255/+173
|
* Update German translationTim Sabsch2023-03-031-217/+201
|
* Update Korean translationSeong-ho Cho2023-03-031-251/+221
|
* Update Czech translationMarek Černocký2023-03-031-262/+183
|
* Merge branch 'wip/rishi/kcm-notification' into 'master'Ray Strode2023-03-011-31/+57
|\ | | | | | | | | kerberos-identity-manager: Use notifications for KCM credential caches See merge request GNOME/gnome-online-accounts!61
| * kerberos-identity-manager: Use notifications for KCM credential cachesDebarshi Ray2023-03-011-0/+30
| | | | | | | | https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/61
| * kerberos-identity-manager: Shuffle some code aroundDebarshi Ray2023-03-011-31/+26
| | | | | | | | | | | | | | | | | | A subsequent commit will start using notifications from Kerberos KCM credential caches as supported by the KCM implementation in SSSD. This rearranges the code to make it easier to enable notifications for different credential cache types. https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/61
| * kerberos-identity-manager: Style fixesDebarshi Ray2023-03-011-2/+3
|/ | | | https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/61
* Update Finnish translationJiri Grönroos2023-02-281-190/+154
|
* Post-release version bump to 3.47.2Emmanuele Bassi2023-02-261-1/+1
|
* Release gnome-online-accounts 3.47.13.47.1Emmanuele Bassi2023-02-261-0/+10
|
* Update Slovenian translationMatej Urbančič2023-02-261-268/+241
|
* Update Danish translationAlan Mortensen2023-02-261-257/+228
|
* Update Bulgarian translationAlexander Shopov2023-02-261-202/+173
|
* Update Basque translationAsier Sarasua Garmendia2023-02-261-253/+229
|
* Merge branch 'support-tardy-or-crashy-identity-service' into 'master'Ray Strode2023-02-233-62/+51
|\ | | | | | | | | Catch more cases where ticket reinitialization is broken See merge request GNOME/gnome-online-accounts!120
| * goakerberosidentity: Ensure old_verification_level is initializedRay Strode2023-02-221-4/+4
| | | | | | | | | | | | | | | | | | | | verify_identity has a short-circuit at the top of the file if the active credentials cache is already known. In that case it bypasses the search for a credentials cache. Unfortunately it also inadvertently bypasses initialization of old_verification_level, leading to the code thinking the identity is always going unexpired. This commit fixes that.
| * goakerberosidentitymanager: Ensure identity-expired signal is emitted from ↵Ray Strode2023-02-221-2/+19
| | | | | | | | | | | | | | | | | | | | | | main loop thread Right now most of the the identity manager signals get emitted from the main thread. This makes sense, and is what a caller would typically expect (given they connect their callbacks in the main thread as well). The one exception is "identity-expired" which gets emitted from the worker thread. This commit fixes that.
| * goakerberosidentity: Queue is-signed-in notify before emitting expired signalRay Strode2023-02-221-15/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now the "expired" signal is emitted before the "is-signed-in" property notification is queued. This notification is used to update the "IsSignedIn" property of the object on the bus. The "expired" signal emission leads to a corresponding "identity-expired" signal on the manager object. A handler for that signal calls into gnome-online-accounts to check identity status. In response, gnome-online-accounts will check the "IsSignedIn" property. This commit makes sure the "is-signed-in" notification is queued first, before the "expired" signal is emitted. Of course queuing the notify before "expired" is emitted isn't enough to ensure the notify happens in time. A future commit will make sure the "identity-expired" signal itself is deferred to the main thread, which should resolve that problem.
| * goakerberosidentity: Ensure properties are updated in a timely fashionRay Strode2023-02-221-1/+1
| | | | | | | | | | | | | | | | | | | | At the moment property notifications of identity objects are deferred to a lower priority idle handler. This is suboptimal because it means there can be a bit of a delay updating the status of, e.g., IsSignedIn, over the bus. This commit changes the notification to queue at normal priority.
| * goakerberosidentity: Don't send "expired" and "unexpired" signals from two ↵Ray Strode2023-02-221-36/+6
| | | | | | | | | | | | | | | | | | | | | | | | parts of the code Since commit e869642bd079aec2098542a3c8f1b296694499ab verify_identity handles sending "expired" and "unexpired" signals on its own. Unfortunately that commit neglected to make goa_kerberos_identity_refresh stop sending the signals. This commit removes the duplicated logic.
| * goakerberosidentity: Ensure credentials of expired identities at startupRay Strode2023-02-221-4/+16
| | | | | | | | | | | | | | | | | | If the identity service is started later than goa-daemon then it won't currently notify goa-daemon about tickets that expired before it was running. This commit fixes the problem by manually calling EnsureCredentials on all signed out identities after their initial enumeration.
* | Update Turkish translationSabri Ünal2023-02-221-34/+34
| |
* | Updated Spanish translationDaniel2023-02-211-259/+230
| |
* | Update Serbian translationМарко Костић2023-02-161-250/+222
| |
* | Update Lithuanian translationAurimas Černius2023-02-131-255/+225
| |
* | Update Occitan translationQuentin PAGÈS2023-02-121-194/+168
| |
* | Update Hebrew translationYaron Shahrabani2023-02-121-33/+28
| |
* | Update Persian translationDanial Behzadi2023-02-111-231/+208
|/
* Update Galician translationFran Dieguez2023-02-051-195/+169
|
* Merge branch '243-error-in-solving-nextcloud-account-address' into 'master'Emmanuele Bassi2023-02-023-5/+8
|\ | | | | | | | | | | | | Resolve "Error in solving Nextcloud account address" Closes #243 See merge request GNOME/gnome-online-accounts!119
| * goaowncloudprovider: Encode user name in calendar/contacts/files URIMilan Crha2023-01-311-1/+4
| | | | | | | | | | | | | | | | | | The GUri is constructed with a flag claiming its parts are already encoded, but when writing verbatim identity as a user name part, it can break parsing the GUri back from a string when the identity contains special characters like an `@`. Writing encoded identity to such GUri fixes the problem. Closes https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/243
| * misc: Use G_URI_FLAGS_PARSE_RELAXED for g_uri_parse() callsMilan Crha2023-01-313-4/+4
|/ | | | | | | That can help when parsing URIs with user name, which contains `@` in an unencoded form, because without it the parsing ends on the first `@`, constructing the host name as `email.com@server.example.com`, which is clearly an incorrect host name.
* Update Indonesian translationKukuh Syafaat2023-01-301-253/+223
|
* Update Portuguese translationHugo Carvalho2023-01-251-206/+184
|
* Update Hebrew translationYosef Or Boczko2023-01-251-189/+165
|
* Update Friulian translationFabio Tomat2023-01-211-263/+231
|
* Update Georgian translationEkaterine Papava2023-01-201-193/+168
|
View Lorry Controller Status