| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When creating the initial user using the gnome-initial-setup user
itself, the session started by gdm is not a regular user session
and so the keyring is not expected to run as usual via the gdm-password
PAM service.
To properly manage the login keyring for online accounts in order
to hand it off successfully to the newly created user, we must both
unlock the keyring initially with an actual password (as gnome-keyring
will simply ignore a null or empty password) and also update that
keyring's password once the user has chosen their password directly
before automatically logging into the new user's session.
In the case that we are not creating a new user via the gnome-initial-setup
user session, there is no need for any of this because the keyring is
already expected to be running as the new user has already logged into
a regular user session.
|
|
|
|
| |
This reverts commit 5bad07a71269869b34d340c2ce4396e56e0538cf.
|
|
|
|
| |
This reverts commit 02168722cfd18cdc0213c0d3270f04f8c5dbd375.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the locale changes then all of the GisPages are rebuilt and
added to the already visible assistant widget - resulting in the
new timezone page being immediately mapped. The result is that
geolocation lookup is immediately cancelled and never gets a chance
to complete if a language is ever selected.
As the current code assumes that the widget is only mapped when it is
actually displayed (which is only true when the parent assistant is
not yet mapped when the child page is added) - Changed the code to
use the explicit gis_page_shown() api instead.
This performs the same intended geolocation lookup cancellation, only
in a more reliable codepath.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Always reset the org.gnome.system.locale.region GSetting property when
running g-i-s, to ensure that the language used for region-dependant
format strings is consistent with the language selected by the user.
https://bugzilla.gnome.org/show_bug.cgi?id=754522
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
| |
The current case-sensitive sorting is confusing.
https://bugzilla.gnome.org/show_bug.cgi?id=755233
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 2587b774490718c962a5da73beec9e060ab202b6.
https://bugzilla.gnome.org/show_bug.cgi?id=754213
|
|
|
|
|
|
| |
This reverts commit b7f05cf285c0809563b51a0f9981c53d62c2f0bb.
https://bugzilla.gnome.org/show_bug.cgi?id=754213
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If we're constructing a GeoClue proxy when the page gets finalized, we
don't actually cancel the GeoClue operations, because we forgot to
create a cancellable.
Spotted-by: Mario Sanchez Prada <mario@endlessm.com>
|
|
|
|
|
|
|
|
|
|
| |
The driver needs to hold an internal copy of the password,
so the password isn't freed at an inopportune moment.
For symmetry, this commit also takes a reference on the
user object that is passed at the same time.
https://bugzilla.gnome.org/show_bug.cgi?id=752980
|
|
|
|
|
|
|
|
|
|
|
| |
The summary page expects the act-user object to be set in
the driver. That only happens at the moment for local
users, not enterprise login users.
This commit fixes things, so it happens for enterprise login
users as well.
https://bugzilla.gnome.org/show_bug.cgi?id=752980
|
|
|
|
|
|
|
|
|
|
|
| |
Right now we detect an enterprise account by the lack of an
ActUser object. That can't work going forward though, since other
bits of the code need an ActUser object for enterprise accounts.
This commit adds the account mode to the driver and changes the
password page to look at the account mode directly.
https://bugzilla.gnome.org/show_bug.cgi?id=752980
|
|
|
|
|
|
| |
It will happen automatically by the pam stack
https://bugzilla.gnome.org/show_bug.cgi?id=752980
|
| |
|
| |
|
|
|
|
|
|
|
| |
geoclue does not deal well with starting clients multiple times
without a stop call in between. This was causing us to loose
geolocation (and incur critical warnings) after a language change
forces reconstruction of all pages.
|
| |
|
| |
|
|
|
|
| |
Not needed anymore.
|
|
|
|
|
|
|
|
|
|
| |
There is a race between the welcome tour script removing the marker
file, and gnome-session notificing that it is gone and killing the
autostarted script. If the script wins the race and manages to start
yelp first, things work ok, but if gnome-session wins the race, yelp
never shows up.
Fix this by only removing the file after yelp is launched.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
We were not careful enough in managing our timeout. Sometimes,
an old timeout could stick around, and then access disposed
objects later on, leading to crash.
https://bugzilla.gnome.org/show_bug.cgi?id=752134
|
| |
|