summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* pam: add little test module for new pam extensionswip/rstrode/list-extensionRay Strode2017-07-262-0/+157
| | | | | This commit just adds a test module for the new pam interface (mainly for documentation purposes)
* libgdm: add api for getting at ChoiceList interfaceRay Strode2017-07-262-2/+215
| | | | This provides gnome-shell with a way to use the new interface.
* daemon: add ChoiceList PAM extensionRay Strode2017-07-264-2/+227
| | | | | | | | | | | | | | This commit adds one PAM extension, a "Choice List" using the new PAM_BINARY_PROMPT protocol added in the previous commit. The PAM module sends a list of (key, row text) pairs, and GDM ferries the request to gnome-shell using a new user verifier sub-interface. gnome-shell should present the list to the user and pass back the corresponding key, which GDM ferries back to the PAM module. Note this commit is only the daemon side. A subsequent commit will add the libgdm API needed for gnome-shell to actually deal with this new PAM extension.
* daemon: introduce pam extension mechanismRay Strode2017-07-2611-12/+342
| | | | | | | | | | | | | | | This abuses PAM_BINARY_PROMPT for our own nefarious purposes. The way it works is GDM advertises what "extensions" it supports with the environment variable, GDM_SUPPORTED_PAM_EXTENSIONS (a space separated list of reverse dns notation names). PAM services that support this protocol, will read the environment variable, and check for extension strings they support. They then know that sending PAM_BINARY_PROMPT won't blow up, and know what format to use for the binary data. The type field of the structure is the index of the string from the environment variable. This commit is just foundation work. It doesn't actually add any extensions.
* session-worker: rename response_text to responseRay Strode2017-07-171-9/+9
| | | | | | | | | Right now we always give text responses back to pam modules, so the response variable is named response_text. That's going to change in the future, when we introduce private protocol for the module to talk to GDM. As prep work for that change, rename "response_text" to "response".
* session: ensure wayland paths get searched even with ↵Daniel van Vugt2017-07-171-1/+0
| | | | | | | | | | | | | | | | | | | | --disable-user-display-server get_system_session_dirs is function that says which directories to search for session desktop files. The returned directories may be xsession dirs, wayland-session dirs, or both, depending on configuration. A bug in this function means an unused NULL sentinal value from the xsession list of directories is getting copied into the middle of the output list, when --disable-user-display-server is passed to configure. This commit corrects the bug, by dropping the unused sentinal value. Launchpad-Bug: 1704050 https://bugzilla.gnome.org/show_bug.cgi?id=784891
* Update Slovak translationDušan Kazik2017-07-131-19/+19
|
* Update Indonesian translationKukuh Syafaat2017-07-111-23/+23
|
* Updated Lithuanian translationAurimas Černius2017-07-101-21/+30
|
* Update Friulian translationFabio Tomat2017-07-071-21/+21
|
* Update Spanish translationDaniel Mustieles2017-07-061-22/+30
|
* Update German translationMario Blättermann2017-07-031-19/+18
|
* Update Hungarian translationBalázs Meskó2017-07-021-24/+22
|
* updated Punjabi TranslationA S Alam2017-06-301-69/+78
|
* Revert "Drop locked down /org/gnome/desktop/session/session-name setting"Ray Strode2017-06-291-0/+1
| | | | | | This reverts commit 9fb36b5bef44bfe4aa1dda52196e08480638ce35. https://bugzilla.gnome.org/show_bug.cgi?id=784340
* data: Add gnome-login.sessionJeremy Bicha2017-06-293-1/+16
| | | | | | | | | | | | | This reverts https://git.gnome.org/browse/gdm/commit/?id=f66cdfcb2 and renames the session from gdm-shell to gnome-login. The removal caused problems for Ubuntu 17.10 which does not include gnome.session by default. https://launchpad.net/bugs/1701243 https://bugzilla.gnome.org/show_bug.cgi?id=784340
* Update Belarusian translationYuras Shumovich2017-06-281-12/+12
|
* Update Kazakh translationBaurzhan Muftakhidinov2017-06-231-12/+12
|
* Use Unicode in translatable stringsPiotr Drąg2017-06-225-11/+11
| | | | | | See https://developer.gnome.org/hig/stable/typography.html https://bugzilla.gnome.org/show_bug.cgi?id=772203
* configure: bump to 3.25.33.25.3Ray Strode2017-06-221-1/+1
|
* NEWS: update for releaseRay Strode2017-06-221-0/+10
|
* build-goo: fix distcheckRay Strode2017-06-223-18/+9
|
* Updated Czech translationMarek Cernocky2017-06-201-40/+44
|
* Updated Spanish translationDaniel Mustieles2017-06-191-36/+41
|
* manager: stop greeter explicitly when finishing displayRay Strode2017-05-081-0/+1
| | | | | | | | | | If GDM shuts down while the login screen is active, we fail to kill off the login screen session. This commit fixes that, by explicitly stopping the greeter session on the display (if there is one) https://bugzilla.gnome.org/show_bug.cgi?id=780213
* Update Kazakh translationBaurzhan Muftakhidinov2017-05-061-37/+41
| | | | (cherry picked from commit 5cd92e6594a945b58c668b4d177993e62a0eced2)
* Updated Slovenian translationMatej Urbančič2017-05-051-43/+47
|
* manager: update session-id property when reusing displayRay Strode2017-05-041-4/+8
| | | | | | | | | | | If a display starts out its life as a greeter display, and then gets reused for the user session, we need to update the session-id property on the display to match its new session. This is important so the reauthentication mechanism is able to match the session with existing display and run in the proper context. https://bugzilla.gnome.org/show_bug.cgi?id=782182
* session: update session type when session is readRay Strode2017-05-041-7/+9
| | | | | | | | | | | | | | | We currently update the session type (to either wayland or x11) when we first start the PAM conversation and later when the username is set (if the user is not set at the same time as the PAM conversation). There's a race that means the session won't necessarly have been read from accountsservice at these points. This commit changes the code to instead update the session type in result to the session actually getting read. https://bugzilla.gnome.org/show_bug.cgi?id=781825
* Update Friulian translationFabio Tomat2017-04-301-9/+8
|
* Updated Serbian translationМирослав Николић2017-04-302-102/+103
|
* dconf defaults: Restore session-name overrideJeremy Bicha2017-04-261-0/+3
| | | | | | | This was dropped in f66cdfcb but GDM won't start when the default session-name is set to something else https://bugzilla.gnome.org/show_bug.cgi?id=781793
* Update French translationCharles Monzat2017-04-241-40/+47
| | | | (cherry picked from commit 1ecfe06c3fde4dfae6c0c900568b426ff0b561a5)
* data: remove stray -n passed to testRay Strode2017-04-191-1/+1
|
* data: install systemd unit even if unit dir already existsDJ Lucas2017-04-191-1/+4
| | | | | | | | | | | A logic error in the Makefile means that the systemd unit will only get installed if the unit dir doesn't yet exist. That's normally the case for package builds, but won't be the case at all for builds from tarball. This commit fixes up the logic. https://bugzilla.gnome.org/show_bug.cgi?id=781082
* manager: fix crash if session fails to startRay Strode2017-04-171-1/+2
| | | | | | | | | | commit 5c9e120594839b0597bc7bb8d06be7ba1076c0d8 attempts to handle a session failing to start, but messages up the signal prototype leading to crash. This commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=781413
* Update Belarusian translationYuras Shumovich2017-04-151-12/+16
| | | | (cherry picked from commit c53b0595a7daee795179b2bd08af28734ce5ffd5)
* Drop locked down /org/gnome/desktop/session/session-name settingMario Sanchez Prada2017-04-131-1/+0
| | | | | | | This is no longer set in the 00-upstream-settings defaults key file since commit f66cdfcb, so no point on locking it down here. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* configure: bump to 3.24.13.24.1Ray Strode2017-04-121-1/+1
|
* NEWS: update for releaseRay Strode2017-04-121-0/+10
|
* manager: stop transient greeter session when done with itRay Strode2017-04-121-0/+20
| | | | | | | | | | | | | If we're running in legacy display mode, we currently can end up with a leaked greeter following user switching. That can happen if a user with an already running session is reauthenticated (so the login screen won't morph into the use session). This commit makes sure we kill the greeter session off in that case. https://bugzilla.gnome.org/show_bug.cgi?id=780939
* manager: make sure we end up on a login screenRay Strode2017-04-121-0/+128
| | | | | | | | | | | | | | | | If we're running in legacy mode where VT1 is not necessarily a login screen, then we can end up in a situation where logging out leaves us sitting on the wrong vt. 1) log in to user 1 on vt 1 2) switch user to login screen on vt 2 and log in as user 2 on vt 2 3) switch user to login screen on vt 3 and unlock user 1 back on vt 1 4) log out of user 1 on vt 1 5) now sitting at blank vt 1 This commit makes sure in that case we jump to a login screen https://bugzilla.gnome.org/show_bug.cgi?id=780914
* Update Italian translationMilo Casagrande2017-04-111-457/+453
|
* Update Greek translationTom Tryfonidis2017-04-081-43/+47
|
* Update Croatian translationgogo2017-04-081-891/+159
|
* Updated Danish translationAsk Hjorth Larsen2017-04-081-37/+42
|
* Update Korean translationChangwoo Ryu2017-04-081-40/+48
|
* Update Indonesian translationKukuh Syafaat2017-04-081-36/+40
|
* Update Hungarian translationBalázs Úr2017-04-051-53/+49
|
* Update German translationMario Blättermann2017-04-051-49/+45
|
View Lorry Controller Status