summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update Hungarian translationgnome-3-26Balázs Úr2023-04-021-291/+1287
|
* Update Chinese (China) translationTong Hui2018-05-221-72/+88
|
* Update Scottish Gaelic translationGNOME Translation Robot2018-02-261-128/+133
|
* Update Afrikaans translationPieter Schalk Schoeman2017-12-181-910/+115
|
* Update Arabic translationKhaled Hosny2017-12-101-34/+42
|
* Update Nepali translationPawan Chitrakar2017-11-071-26/+36
|
* Updated Norwegian bokmål translation.Kjartan Maraas2017-11-061-69/+77
|
* configure: bump to 3.26.2.13.26.2.1Ray Strode2017-10-311-1/+1
|
* NEWS: update for releaseRay Strode2017-10-311-0/+5
|
* session-worker: Use g_variant_dup_string where possibleJan Alexander Steffens (heftig)2017-10-311-8/+8
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=789722
* session: don't call gdm_session_defaults_changed from setupRay Strode2017-10-311-2/+0
| | | | | | | It's only needed to update the session type, which we do earlier in the function anyway. https://bugzilla.gnome.org/show_bug.cgi?id=789722
* session-worker: Adjust Initialize to behave more like SetupFor*Jan Alexander Steffens (heftig)2017-10-311-8/+31
| | | | | | Most importantly, wait for the user settings to be loaded. https://bugzilla.gnome.org/show_bug.cgi?id=789722
* configure: bump to 3.26.23.26.2Ray Strode2017-10-301-1/+1
|
* NEWS: update for releaseRay Strode2017-10-301-0/+10
|
* display: don't mark initial-setup ran until it ranRay Strode2017-10-241-10/+12
| | | | | | | | | | We don't want to skip running initial setup if wayland fell back or something. This commit makes sure we only stop trying to start initial-setup after it's completed. https://bugzilla.gnome.org/show_bug.cgi?id=789434
* libgdm: add api for getting at ChoiceList interfaceRay Strode2017-10-202-2/+218
| | | | | | This provides gnome-shell with a way to use the new interface. https://bugzilla.gnome.org/show_bug.cgi?id=788851
* daemon: add ChoiceList PAM extensionRay Strode2017-10-204-2/+234
| | | | | | | | | | | | | | | | 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. https://bugzilla.gnome.org/show_bug.cgi?id=788851
* daemon: introduce pam extension mechanismRay Strode2017-10-2010-14/+325
| | | | | | | | | | | | | | | | | 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. https://bugzilla.gnome.org/show_bug.cgi?id=788851
* session: add new Initialize methodRay Strode2017-10-203-169/+98
| | | | | | | | | | | | | Right now the worker interface has three methods for starting a conversation: Setup, SetupForUser, SetupForProgram Each of these method calls take a large number of overlapping arguments. Extending these argument lists is painful and breaks upgrades. This commit adds a new, fourth call, Initialize, which supercedes the others and just takes a vardict, which is much more extensible. https://bugzilla.gnome.org/show_bug.cgi?id=788851
* session-worker: rename response_text to responseRay Strode2017-10-201-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". https://bugzilla.gnome.org/show_bug.cgi?id=788851
* Ignore session IDs ending with "-xorg" under X11Olivier Tilloy2017-10-171-0/+18
| | | | | | | | | | This is done under the assumption that they are meant for Wayland only. It is expected that a session called "foo" would have a "foo.desktop" file under wayland-sessions/, a fallback "foo.desktop" under xsessions/, and another "foo-xorg.desktop" under xsessions (that may simply be a symlink to "foo.desktop") specifically for Wayland. https://bugzilla.gnome.org/show_bug.cgi?id=788552
* manager: fix compile warningRay Strode2017-10-131-2/+2
| | | | | | | | | | commit 7e8243eecd0233f7ab92519207f2520794439b11 introduced a compiler warning if gdm is built with --enable-wayland and --disable-user-display-server This commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=788963
* dconf: Set universal-access icon to always showFlorian Müllner2017-10-131-0/+3
| | | | | | | This used to be done with a special greeter indicator, but it's much simpler to just define the presets accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=788942
* legacy-display: ensure X server is dead when respawningRay Strode2017-10-101-0/+21
| | | | | | | | | | | | If the user logs out we may detect the session dying before we detect the X server dying. If that happens, then we currently don't wait for the X server to exit before starting a new X server. This commit makes sure to explicitly kill the X server and wait for its death before proceeding. https://bugzilla.gnome.org/show_bug.cgi?id=788786
* manager: don't record wtmp entries when user unknownRay Strode2017-10-102-14/+6
| | | | | | | | | | | | | Right now we end up writing wtmp entries for the login screen user into /var/log/wtmp, but with a funky username of "(unknown)". The login screen session shouldn't get a wtmp entry, and we shouldn't ever add wtmp entries for sessions we don't know the username for. This commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=788784
* [l10n] Updated Catalan (Valencian) translationXavi Ivars2017-10-051-197/+96
|
* configure: bump to 3.26.13.26.1Ray Strode2017-10-031-1/+1
|
* NEWS: update for releaseRay Strode2017-10-031-0/+10
|
* Use standard exit codes.Robert Ancell2017-10-0313-52/+44
| | | | | | | | | Use EXIT_ defines for readibility. There were some exit codes > 1, but they don't seem to be checked by any of the parent process code. This does mean that the logs might have changed, but modern logging techniques have probably made this obsolete. https://bugzilla.gnome.org/show_bug.cgi?id=788307
* Revert "common: Also set GROUP in scripts"Ray Strode2017-10-031-26/+0
| | | | This reverts commit 6594b1f262ffaa3d120c0b23f92bad2802f17e4a.
* common: Also set GROUP in scriptsSam Spilsbury2017-10-031-0/+26
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787287
* display: Allow user to set gnome.initial-setup=(0|1)Sam Spilsbury2017-10-031-0/+119
| | | | | | This will either force the initial setup to run or not to run Fixes #787286
* gschema: Fix gettext-domainPiotr Drąg2017-09-301-1/+2
|
* daemon: Remove obsolete module gdm-xerrorsRobert Ancell2017-09-285-285/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=788303
* daemon: Tidy up main() failure casesRobert Ancell2017-09-281-17/+7
| | | | | | | | | Remove goto that no longer does anything. Consistently use return instead of exit() from main. Print pre-log errors to stderr to ensure they're visible regardless of GLib settings. https://bugzilla.gnome.org/show_bug.cgi?id=788302
* daemon: Move root check before settings are loadedRobert Ancell2017-09-281-7/+7
| | | | | | | The root check doesn't require settings and may be the cause of settings failing to load. https://bugzilla.gnome.org/show_bug.cgi?id=788301
* daemon: Fix double free of GErrorRobert Ancell2017-09-281-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=788300
* daemon: Remove unnecessary check for function that can't return NULLRobert Ancell2017-09-281-5/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=788299
* Update Icelandic translationSveinn í Felli2017-09-251-15/+24
|
* Update Persian translationsArash Mousavi2017-09-221-67/+72
|
* launch-environment: don't name greeter log $display-greeter.log with user ↵Ray Strode2017-09-211-1/+5
| | | | | | | | | | displays If the X server is started as part of the session, we don't know the display up front. So don't try to encode the display in the log in that case. https://bugzilla.gnome.org/show_bug.cgi?id=787989
* xdmcp-display-factory: more signal prototype fixingRay Strode2017-09-211-4/+3
| | | | | | | | | | | | | | | | | | | commit 2a3d5a7c402534c3611956fed930394a51cb00c5 attempted to fix the signal prototype of on_client_disconnected to match the marshalled arguments. Unfortunately, the handler is used for two different signals: 1) when a user chooses "Disconnect" from the chooser menu 2) when a user closes the Xephyr window (or turns off the thin client or whatever) The signals have slightly different prototypes, so commit 2a3d5a7c fixed 2), but broke 1). This commit massages the signal connections and handler signature to work for both cases. https://bugzilla.gnome.org/show_bug.cgi?id=787987
* gdm-sessions: force a session bus for non-seat0 sessionRay Strode2017-09-201-1/+6
| | | | | | | | | | | | | | | | Eventually, our software should become "multi-seat aware", where it takes into account multiple seats at a time for the user (even if it's just putting up a dialog saying "user is busy" on all but one seat). We're not there yet. And user bus currently breaks XDMCP (which should really spawn session with its own separate user, but again, we're not there yet). This commit changes GDM to start a session bus for all non-seat0 displays, as a near-term workaround. https://bugzilla.gnome.org/show_bug.cgi?id=787943
* session-worker: only jump to VT on seat0Ray Strode2017-09-201-4/+8
| | | | | | | seat0 is the only seat that supports VTs, so don't ever try to change VTs if not on seat0. https://bugzilla.gnome.org/show_bug.cgi?id=787943
* Updated Slovenian translationMatej Urbančič2017-09-201-23/+22
|
* daemon,libgdm: allow wayland sessions with --disable-user-display-serverRay Strode2017-09-192-1/+3
| | | | | | | | | | | | Right now we hide wayland sessions from the list if the greeter isn't wayland. The greeter is never wayland if built with --disable-user-display-server. This commit allows wayland sessions for the user session, when --disable-user-display-server --enable-wayland-support is specified, even though the greeter won't use wayland itself. https://bugzilla.gnome.org/show_bug.cgi?id=787899
* Update Russian translationStas Solovey2017-09-181-24/+23
|
* gdm-session: always pass down user saved languageMario Sanchez Prada2017-09-181-2/+1
| | | | | | | | | | | | | | | | There's a bug when changing the language of the login screen to a different one than the user session's language, which causes the new language to be used both in the login screen AND the user session if you simply logout and then re-login without rebooting. Restarting the machine after that point normalizes things, getting the new language used only in the login screen but not in the user session. Making sure that the user language is always saved by the session seems without checking whether is the same than the default language fixes this. Based on a patch by Felipe Erias Morandeira <femorandeira@igalia.com> https://bugzilla.gnome.org/show_bug.cgi?id=786422
* daemon: check for Xwayland availabilityFrederic Crozat2017-09-181-1/+1
| | | | | | | prevent gnome-shell crash when testing Wayland session if Xwayland isn't installed. https://bugzilla.gnome.org/show_bug.cgi?787837
* Update Greek translationEfstathios Iosifidis2017-09-121-29/+29
|
View Lorry Controller Status