summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* dconf defaults: Remove deprecated a11y related keysMario Sanchez Prada2017-04-041-6/+0
| | | | | | | This are ignored by GTK3 and GNOME Shell now, and are only relevant for GTK2 and other legacy apps now, not for GDM or gnome-initial-setup. https://bugzilla.gnome.org/show_bug.cgi?id=780866
* launch-environment: Don't set DCONF_PROFILE for gnome-initial-setupDaniel Drake2017-04-041-2/+6
| | | | | | | | The locked down dconf profile should not be used for the initial setup session. This allows overridden values from the user profile to take effect. https://bugzilla.gnome.org/show_bug.cgi?id=780866
* Update Russian translationStas Solovey2017-04-031-47/+43
|
* local-display-factory: add missing comma to fix user switchingRay Strode2017-04-031-1/+1
| | | | | | | | | | commit 4b47633b36a22195e7976a8e597862eff695ca86 refactored some code and inadvertently dropped an important comma, which broke user switching. This commit reintroduces the comma. https://bugzilla.gnome.org/show_bug.cgi?id=780879
* Revert "launch-environment: Don't set DCONF_PROFILE for gnome-initial-setup"Mario Sanchez Prada2017-04-031-6/+2
| | | | | | | | | This should never have landed in the first place (I committed it by mistake while pushing the patch for bug 780862) and according to the discussion in bug 780866, it seems clear that this is not an upstreamable patch, not at least in its current form. This reverts commit 67ef79c125c34b66072ae00927b2c89f2c98f196.
* Makefile: Move to AM_DISTCHECK_CONFIGURE_FLAGSSam Spilsbury2017-04-032-2/+2
| | | | | | | Since automake 1.11.2 it is recommended that packages use AM_DISTCHECK_CONFIGURE_FLAGS instead of DISTCHECK_CONFIGURE_FLAGS as the latter is intended to be a user variable.
* launch-environment: Don't set DCONF_PROFILE for gnome-initial-setupDaniel Drake2017-04-031-2/+6
| | | | | | The locked down dconf profile should not be used for the initial setup session. This allows overridden values from the user profile to take effect.
* Updated Lithuanian translationAurimas Černius2017-04-021-39/+44
|
* Update Latvian translationRūdolfs Mazurs2017-04-021-53/+51
|
* Update Friulian translationFabio Tomat2017-04-011-38/+43
|
* manager: add #ifdef HAVE_LIBXDMCP in a couple placesRay Strode2017-04-011-4/+11
| | | | | | | | | | | | | | halfline: gdm fails to build in Continuous: http://build.gnome.org/continuous/buildmaster/builds/2017/04/01/11/build/log-gdm.txt gdm-manager.o: In function `set_up_session': /ostbuild/source/gdm/_build/daemon/../../daemon/gdm-manager.c:1453: undefined reference to `gdm_xdmcp_chooser_display_get_type' gdm-manager.o: In function `gdm_manager_handle_open_session': /ostbuild/source/gdm/_build/daemon/../../daemon/gdm-manager.c:846: undefined reference to `gdm_xdmcp_chooser_display_get_type' https://bugzilla.gnome.org/show_bug.cgi?id=780813
* Update Swedish translationAnders Jonsson2017-04-011-38/+42
|
* Update Polish translationPiotr Drąg2017-04-011-26/+30
|
* Update Slovak translationDušan Kazik2017-04-011-39/+43
|
* Update Brazilian Portuguese translationRafael Fontenelle2017-03-311-46/+51
|
* chooser: filter out duplicate hostnamesRay Strode2017-03-311-1/+33
| | | | | | | | | | One host may report itself on multiple interfaces. GDM only supports based on hostname not interface, so that leads duplicate entries in the list. This commit filters out the dupes. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* chooser: switch to browse selection modeRay Strode2017-03-311-1/+8
| | | | | | | The chooser is a host browser after all. It makes not sense to have an unselected item. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* chooser: make host list fill the dialogRay Strode2017-03-311-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=780787
* chooser: fix duplicate entry in the listRay Strode2017-03-311-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=780787
* xdmcp-display-factory: explicitly stop greeter session on disconnectRay Strode2017-03-311-0/+1
| | | | | | If the client disconnects, we should kill off the necessary processes. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* xdmcp-display-factory: fix signal prototypeRay Strode2017-03-311-1/+2
| | | | | | | The callback was getting called with the wrong arguments leading to spew in the logs and necessary code not getting run! https://bugzilla.gnome.org/show_bug.cgi?id=780787
* xdmcp-display: don't set MANAGED until we've connectedRay Strode2017-03-311-2/+1
| | | | | | | | | | | We don't want to start the greeter session until we've successfully connected to the display ourselves! This prevents a race where session processes may inadvertently get the initial connection to the display server, causing premature resets. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* manager: fix up support for chooserRay Strode2017-03-311-9/+53
| | | | | | | | | | We were missing some chunks of code to handle dealing with the chooser. This commit adds in the necessary bits to start the chooser, and deal with the choice. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* launch-environment: implement hostname-selected signalRay Strode2017-03-312-0/+29
| | | | | | | | | | | We're connecting to a signal that isn't implemented. This commit adds the implementation. A slightly better fix might be to cut out some of the layers, of middle men passing around hostname-selected, but for now this is fine. https://bugzilla.gnome.org/show_bug.cgi?id=780787
* manager: drop some erroneous codeRay Strode2017-03-311-18/+0
| | | | | | | This is commit 82296a3350b64d0ed5ae3b9f6983466c60dd8a53 all over again. The code snuck back in during a refactor ! https://bugzilla.gnome.org/show_bug.cgi?id=780787
* launch-environment: fix crasher when session-mode isn't setRay Strode2017-03-271-6/+7
| | | | | | This commit fixes a crasher when starting the indirect chooser. https://bugzilla.gnome.org/show_bug.cgi?id=780618
* dconf defaults: Remove obsolete configurationBastien Nocera2017-03-272-4/+0
| | | | | | | | | | gnome-settings-daemon will not use dconf to know which plugin (now helper daemon) to run anymore. Instead, this logic will be implemented directly in gnome-settings-daemon. See https://bugzilla.gnome.org/show_bug.cgi?id=772370 https://bugzilla.gnome.org/show_bug.cgi?id=772447
* session: update session search dirs when ignore-wayland changesRay Strode2017-03-251-13/+21
| | | | | | | | | | | Right now the first time the session search dirs are requested, they are computed and cached. That leaves them stale if the ignore-wayland flag changes, which breaks fallback mode in some cases. This commit fix the problem by always computing the session search dirs in full, with no caching. https://bugzilla.gnome.org/show_bug.cgi?id=780518
* manager: if falling back to X11 retry autologinRay Strode2017-03-251-3/+8
| | | | | | | | Right now, we get one shot to autologin. If it fails, we fall back to the greeter. We should give it another go if the reason for the failure was wayland fallback to X. https://bugzilla.gnome.org/show_bug.cgi?id=780520
* configure: bump to 3.24.03.24.0Ray Strode2017-03-201-1/+1
|
* NEWS: update for releaseRay Strode2017-03-201-0/+4
|
* configure: bump to 3.23.923.23.92Ray Strode2017-03-131-1/+1
|
* NEWS: update for releaseRay Strode2017-03-131-0/+5
|
* manager: be more robust against autologin having an invalid userMichael Catanzaro2017-03-102-31/+86
| | | | | | | If the configured autologin user does not exist, fall back to a greeter session. https://bugzilla.gnome.org/show_bug.cgi?id=695250
* configure: bump to 3.23.91.13.23.91.1Ray Strode2017-03-061-1/+1
|
* NEWS: update for releaseRay Strode2017-03-061-0/+10
|
* manager: don't try to activate session if session not on seatRay Strode2017-03-031-4/+6
| | | | | | | | | | | If a session is not associated with a seat (because it's remote), then we shouldn't try to activate the session. Activating sessions, really only means anything on seat0 (where it means to change the active VT). This prevents premature failure before unlock on XDMCP. https://bugzilla.gnome.org/show_bug.cgi?id=779500
* common: limit potentially expensive name lookupsRay Strode2017-03-031-12/+12
| | | | | | | | | | | | Right now we're doing name look ups when we don't have to. These name look ups can cause lengthy timeouts in misconfigured environments. This commit reduces the name looks used by GDM to make it more resiliant to failure. Ported from RHEL 6 to RHEL 7 by Ashish Shah <ashishks@redhat.com> https://bugzilla.gnome.org/show_bug.cgi?id=779499
View Lorry Controller Status