summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* 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
* configure: bump to 3.26.03.26.0Ray Strode2017-09-121-1/+1
|
* NEWS: update for releaseRay Strode2017-09-121-0/+6
|
* 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
* Updated Danish translationAsk Hjorth Larsen2017-09-101-43/+25
|
* Update Basque languageInaki Larranaga Murgoitio2017-09-091-0/+0
|
* Update Basque languageInaki Larranaga Murgoitio2017-09-091-57/+61
|
* configure: bump to 3.25.923.25.92Ray Strode2017-09-081-1/+1
|
* NEWS: update for releaseRay Strode2017-09-081-0/+9
|
* gdm-{wayland,x}-session: omit GNOME_SHELL_SESSION_MODE from environmentXiaoguang Wang2017-09-082-0/+2
| | | | | | | | | | | | | | | | | | | | | | After a user logs out, the systemd --user session may still be running (if, say, the user session was left around in the closing state, because of pulseaudio). If that happens, new user sessions will inherit the environment of previous sessions. Some of these environment variables are already intentionally pruned, DISPLAY, XAUTHORITY, WAYLAND_SOCKET, etc. One environment variable that isn't pruned, but should be, is GNOME_SHELL_SESSION_MODE. If it lingers, users could end up in classic mode even though they picked the non-classic mode from the gear menu. This commit adds GNOME_SHELL_SESSION_MODE to the list of environment variables to prune. (minor changes to original patch and commit message from Ray Strode) https://bugzilla.gnome.org/show_bug.cgi?id=785918
* gdm-{wayland,x}-session: only omit unset session variables from environmentRay Strode2017-09-082-9/+29
| | | | | | | | | | | | | | The display server launcher wrapper scripts try to unset any stale environment variables imported from systemd. There is a possibility, some of these stale variables, however, could be "refreshed" by gdm in the current session. If that's the case, we shouldn't clear them. This reworks the unset calls into a loop, and guards each unset call with a check to make sure it's not in the current environment. https://bugzilla.gnome.org/show_bug.cgi?id=785918
* Update French translationAlain Lojewski2017-09-081-60/+60
|
* Updated Dutch translation Master 3.26hanniedu2017-09-081-375/+101
|
* systemd: send SIGHUP to gdm on reloadSam Spilsbury2017-09-051-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787288
* settings: Make sure to set old settings global to NULL on finalizeSam Spilsbury2017-09-051-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=787288
* Updated Vietnamese translationTrần Ngọc Quân2017-09-041-54/+57
| | | | Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
* Updated Bulgarian translationAlexander Shopov2017-09-021-48/+53
|
* Update Korean translationChangwoo Ryu2017-09-021-21/+21
|
* Update Brazilian Portuguese translationRafael Fontenelle2017-08-301-28/+36
|
* Update Finnish translationJiri Grönroos2017-08-291-65/+72
|
* Update Latvian translationRūdolfs Mazurs2017-08-281-19/+28
|
* Update Chinese (Taiwan) translationCheng-Chia Tseng2017-08-271-57/+61
|
View Lorry Controller Status