summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update Hungarian translationgnome-3-24Balázs Úr2023-04-021-291/+1287
|
* Update Chinese (China) translationTong Hui2018-05-221-72/+88
|
* configure: bump to 3.24.33.24.3Ray Strode2017-09-121-1/+1
|
* NEWS: update for releaseRay Strode2017-09-121-0/+7
|
* gdm-session: Calculate fallback session name without ".desktop"Iain Lane2017-09-121-12/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the user has not ever selected a session from the selector, we will log them into the `fallback' session, which is calculated by looking at all installed sessions and picking the first one in the list. There is a bug that the visually selected session presented in the greeter can be different from the fallback session calculated inside GDM. This happens because the two sort sessions differently. Inside GDM we calculate the fallback session by comparing the full basename of the file: >>> GLib.strcmp0("gnome-xorg.desktop", "gnome.desktop") -1 Whereas gnome-shell calls gdm_get_session_ids(), which returns IDs without the ".desktop" extension. Those are then sorted: >>> GLib.strcmp0("gnome-xorg", "gnome") 45 which gives a different ordering. Fix this bug by calculating the fallback session in the same way, by removing ".desktop" from the filename. https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705157 https://bugzilla.gnome.org/show_bug.cgi?id=787304
* manager: don't allow autologin from transient displaysRay Strode2017-09-121-1/+4
| | | | | | | | | | | | | | | In theory, we're only only supposed to allow autologin the first time a session is run, but we only count a session run, once it's finished. This means that if a user creates a transient session to user switch, before they've logged out the first time at boot up, that transient session will begin autologin as well (which actually gets treated as an auto unlock). This commit makes sure autologin is only ever run on the initial display. https://bugzilla.gnome.org/show_bug.cgi?id=783779
* Update Icelandic translationSveinn í Felli2017-08-231-43/+40
|
* Updated Slovenian translationMatej Urbančič2017-08-071-39/+43
|
* Updated Czech translationMarek Cernocky2017-06-201-41/+45
|
* configure: bump to 3.24.23.24.2Ray Strode2017-05-091-1/+1
|
* NEWS: update for releaseRay Strode2017-05-091-0/+7
|
* manager: stop greeter explicitly when finishing displayRay Strode2017-05-091-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
* manager: update session-id property when reusing displayRay Strode2017-05-091-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-091-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 Kazakh translationBaurzhan Muftakhidinov2017-05-061-37/+41
|
* dconf defaults: Restore session-name overrideJeremy Bicha2017-05-051-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
* Updated Serbian translationМирослав Николић2017-05-042-102/+103
|
* Update French translationCharles Monzat2017-04-241-40/+47
|
* 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
|
* 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
View Lorry Controller Status