summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* slave: kill off clients from display when finishedRay Strode2016-12-131-0/+29
| | | | | | | | | | When we're done with the display we need to kill off any clients that are lingering and close our own connection to the display. This is so, for instance, processes from the session don't stick around on a -noreset Xvnc server (or something) https://bugzilla.gnome.org/show_bug.cgi?id=776059
* worker: kill process group when session exitsRay Strode2016-12-131-0/+2
| | | | | | | Send a hangup signal to the session pg when it exits, so things have a chance to get cleaned up. https://bugzilla.gnome.org/show_bug.cgi?id=776059
* xdmcp-display-factory: notify remote display when session endedRay Strode2016-12-131-1/+14
| | | | | | | | | | | | gnome-shell and the session dbus daemon don't automatically exit when gnome-session does. They, instead, wait for the display to exit or regenerate. If the display is remote, that won't happen until the keep alive timeout. This commit changes GDM to explicitly notify the remote display when the session is over, so that it can regenerate immediately. https://bugzilla.gnome.org/show_bug.cgi?id=776059
* display: port GdmDisplay to xcbRay Strode2016-12-132-97/+121
| | | | | | | | | | Xlib will kill the process if it notices the display connection has gone away. This is suboptimal for the main gdm process! This commit ports the Xlib code to xcb, so it won't have the above fragility. https://bugzilla.gnome.org/show_bug.cgi?id=776059
* display: close X11 connectionRay Strode2016-12-131-0/+8
| | | | | | | We're opening an X11 connection but never closing it, this commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=776059
* manager: make sure we retain ignore-wayland on second loginRay Strode2016-12-051-29/+14
| | | | | | | | | | | | | The intention of the code is to only allow wayland login for user sessions if the greeter session is also wayland. Right now, that intention is only honored the first time a user logs in. This commit corrects the problem, to make sure sure we always avoid wayland if the greeter session avoided wayland. https://bugzilla.gnome.org/show_bug.cgi?id=775659
* daemon: update X11DisplayName on register displayMathias Reck2016-11-102-2/+4
| | | | | | | | | When a display registered, the sessions 'display-name' was already updated. The displays 'x11-display-name' however was not, so I've just added that. Of course that also meant that the 'x11-display-name' could no longer be constructor only. https://bugzilla.gnome.org/show_bug.cgi?id=752341
* configure: bump to 3.22.13.22.1Ray Strode2016-10-121-1/+1
|
* NEWS: update for releaseRay Strode2016-10-121-0/+6
|
* configure: use /usr/bin/X instead of /usr/bin/Xorg by defaultRay Strode2016-10-121-5/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=772319
* wayland-session: don't start new session with stale session env varsRay Strode2016-09-211-0/+7
| | | | | | | | | | | | | | | commit 448134d3cdbc54e5359ea33d387993b0defdaefa changed gdm to import the session from systemd --user. Unfortunately, it broke log in after log out. The problem is, certain session specific environment variables from the previous session were getting leaked into the new session. This commit wipes the ones causing the most problems on the GDM side, but gnome-session should also probably purge them from the systemd --user environment when it exits. https://bugzilla.gnome.org/show_bug.cgi?id=771786
* configure: bump to 3.22.03.22.0Ray Strode2016-09-191-1/+1
|
* NEWS: update for releaseRay Strode2016-09-191-0/+6
|
* Updated Galician translationsFran Dieguez2016-09-111-356/+375
|
* Updated British English translationBruce Cowan2016-09-081-1336/+72
|
* pam-lfs,pam-redhat: get rid of gdm.pamRay Strode2016-09-073-32/+2
| | | | | These files haven't been used since multistack became a hard requirement.
* pam-exherbo,pam-redhat: avoid password-auth/common-authRay Strode2016-09-072-5/+2
| | | | | | | | | | | In theory sending the password to them could be beneficial. If for instance, they have pam_krb5 or pam_ecryptfs or pam_sss. In practice, the stacks will fail if the passwords don't match, and prevent autologin from continuing. This commit just sidesteps them for now. Eventually, authconfig/et al, will need to get updated to accomodate us.
* pam-redhat: don't use substack in autologin caseRay Strode2016-09-061-5/+5
| | | | It prevents postlogin from getting run.
* pam_gdm: Don't return PAM_AUTHINFO_UNAVAIL on successRay Strode2016-09-061-0/+2
| | | | | | | | commit bb12416da1f6 tries to make pam_gdm return AUTHINFO_UNAVAIL if keyutils isn't around, but it inadvertently makes pam_gdm return AUTHINFO_UNAVAIL when the password is available! This commit fixes that.
* Completed Punjabi TranslationA S Alam2016-09-051-348/+65
|
* configure: bump to 3.21.913.21.91Ray Strode2016-08-311-1/+1
|
* NEWS: update for releaseRay Strode2016-08-311-0/+6
|
* gdm-{wayland,x}-session: import environment from systemd managerRay Strode2016-08-312-0/+115
| | | | | | | | The user may have configured the user environment via user.conf or other means. This commit makes sure this session gets those environment changes. https://bugzilla.gnome.org/show_bug.cgi?id=736660
* gdm-wayland-session: keep connection to session bus aliveRay Strode2016-08-311-3/+20
| | | | | | | This makes it behave more like gdm-x-session. Also, we're going to need the connection in a minute. https://bugzilla.gnome.org/show_bug.cgi?id=736660
* pam: don't call into pam_unix if pam_gdm fails for autolgoinRay Strode2016-08-302-2/+2
| | | | | | | | | | | If pam_gdm fails we shouldn't call into pam_unix since it can lead to the system asking for a password, and autologin isn't equipped for that. This commit changes the pam configuration to jump to pam_permit if pam_gdm fails. https://bugzilla.gnome.org/show_bug.cgi?id=770612
* pam_gdm: return AUTHINFO_UNAVAIL if kernel keyring unavailableRay Strode2016-08-301-1/+1
| | | | | | | | right now we return PAM_SUCCESS if keyutils are unavailable. This is the wrong default, we should fail if we aren't able to get the password. https://bugzilla.gnome.org/show_bug.cgi?id=770612
* pam: update gdm-autologin for exherbpMarc-Antoine Perennou2016-08-301-1/+1
| | | | Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
* gdm-{x,wayland}-session: drop dependency on DBUS_SESSION_BUS_ADDRESSRay Strode2016-08-292-28/+42
| | | | | | | | | | | | DBUS_SESSION_BUS_ADDRESS is not the preferred way to find the session bus these days. Instead it's expected to be found at $XDG_RUNTIME_DIR/bus This commit changes the session launcher code, to just try to get a connection to the bus explicitly, instead relying on the presence of DBUS_SESSION_BUS_ADDRESS to know whether to start a fallback bus. https://bugzilla.gnome.org/show_bug.cgi?id=770395
* gdm-x-session: use cancellable in UpdateActivationEnvironment callRay Strode2016-08-291-1/+1
| | | | | | | I just noticed when reading the code that we pass a cancellable into the function, but then don't use it. https://bugzilla.gnome.org/show_bug.cgi?id=770396
* dconf defaults: Drop input-devices/hotplug-commandJeremy Bicha2016-08-252-4/+0
| | | | | | Since it was dropped in gnome-settings-daemon 3.20 https://bugzilla.gnome.org/show_bug.cgi?id=770418
* configure: bump to 3.21.903.21.90Ray Strode2016-08-221-1/+1
|
* NEWS: update for releaseRay Strode2016-08-221-0/+6
|
* Updated Polish translationPiotr Drąg2016-08-221-44/+40
|
* pam: grab cached password from systemd and pass it onRay Strode2016-08-197-7/+53
| | | | | | | | | | | | | If the user has an encrypted disk then systemd will cache the password they type into the keyring. It makes sense to try to use this password for automatic login purposes first, since on single user machines, the sole user password is likely to match the disk password. Of course if it doesn't work we'll fall back to the old way of doing automatic login without a password (and then the user will have to manualy enter if they need to for gnome-keyring or whatever) https://bugzilla.gnome.org/show_bug.cgi?id=769950
* pam_gdm: add stub pam moduleRay Strode2016-08-194-0/+123
| | | | | | | It doesn't do anything yet, but it will eventually get used for autologin purposes, and maybe other things. https://bugzilla.gnome.org/show_bug.cgi?id=769950
* build-gui: fix build when xdmcp is disabledRay Strode2016-08-161-1/+5
|
* Update POTFILES.inPiotr Drąg2016-08-151-2/+2
|
* build-goo: get rid of gui directoryRay Strode2016-08-1514-15/+2
| | | | It only has the chooser in it, so just move the chooser to the toplevel.
* Update Gujarati translationRafael Fontenelle2016-08-021-260/+47
|
* Updated Spanish translationDaniel Mustieles2016-08-021-17/+9
|
* configure: bump to 3.21.43.21.4Ray Strode2016-07-221-1/+1
|
* NEWS: update for releaseRay Strode2016-07-221-0/+6
|
* Add Language headers to po filesPiotr Drąg2016-07-1632-66/+31
| | | | Future versions of gettext will fail if this header is missing.
* Update Arabic translationSafa Alfulaij2016-07-061-13/+13
|
* Updated Arabic translationSafa Alfulaij2016-07-061-261/+51
|
* Updated Indonesian translationAndika Triwidada2016-06-241-50/+34
| | | | (cherry picked from commit 2778a8a85f73dced81acca6ca2d7268572817d78)
* local-display-factory: disconnect signal handlers when factory is disposedRay Strode2016-06-221-11/+15
| | | | | | | | | | | | There's the potential for a crash in the shutdown path after the factory is disposed, since we fail to disconnect signal handlers to the displays / display store at factory dispose time. This commit changes the g_signal_connect to g_signal_connect_object, to avoid any potential for crash. (this is a fix noticed when reading through the source. It's tangentially related to a discussion on irc for a different bug)
* configure: bump to 3.21.33.21.3Ray Strode2016-06-201-1/+1
|
* NEWS: update for releaseRay Strode2016-06-201-0/+5
|
* Updated Indonesian translationAndika Triwidada2016-06-201-1920/+1129
| | | | (cherry picked from commit b5df2d64487923196c288843d9e8ff2e89b90e8b)
View Lorry Controller Status