summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Updated Serbian translationМарко Костић2016-03-201-27/+20
|
* Updated Turkish translationMuhammet Kara2016-03-191-272/+43
|
* Updated Italian translationGianvito Cavasoli2016-03-181-446/+440
|
* configure: bump to 3.19.923.19.92Ray Strode2016-03-151-1/+1
|
* NEWS: update for releaseRay Strode2016-03-151-0/+6
|
* Updated Korean translationChangwoo Ryu2016-03-121-47/+27
|
* Updated Greek translationTom Tryfonidis2016-03-111-59/+44
|
* Updated Hebrew translationYosef Or Boczko2016-03-111-328/+32
|
* Updated Finnish translationJiri Grönroos2016-03-051-186/+42
|
* Update Latvian translationRūdolfs Mazurs2016-03-031-46/+38
|
* manager: fix small leakMichael Catanzaro2016-03-021-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=695250
* Updated Lithuanian translationAurimas Černius2016-03-021-19/+16
|
* configure: bump to 3.19.913.19.91Ray Strode2016-03-021-1/+1
|
* NEWS: update for releaseRay Strode2016-03-021-0/+8
|
* Updated Czech translationMarek Černocký2016-02-271-64/+29
|
* Updated Occitan translationCédric Valmary2016-02-271-149/+51
|
* openembedded: rename gdm pam file to gdm-passwordRay Strode2016-02-242-1/+1
| | | | | | | This is api expected by the shell, it has to be called gdm-password. https://bugzilla.gnome.org/show_bug.cgi?id=762636
* manager: make sure timed login conversation is startedRay Strode2016-02-241-0/+3
| | | | | | | | | At some point in a refactor we apparently stopped starting the PAM conversation used for timed login. This commit adds it back. https://bugzilla.gnome.org/show_bug.cgi?id=762635
* Updated Galician translationsFran Dieguez2016-02-231-274/+35
|
* gdm-{x,wayland}-session: add newlines to g_printerrRay Strode2016-02-232-9/+9
| | | | g_printerr needs newlines or log entries butt up against each other.
* Updated Ukrainian translationDaniel Korostil2016-02-231-264/+36
|
* Update Catalan translationÇJordi Mas2016-02-221-146/+32
|
* Updated Serbian translationМирослав Николић2016-02-192-131/+99
|
* configure: bump to 3.19.903.19.90Ray Strode2016-02-171-1/+1
|
* NEWS: update for releaseRay Strode2016-02-171-0/+8
|
* Updated Swedish translationAnders Jonsson2016-02-171-48/+39
|
* Updated Chinese (Taiwan) translationChao-Hsiung Liao2016-02-131-160/+34
|
* gdm-session: update session type when the session defaults changeRay Strode2016-02-091-2/+2
| | | | | | | | | | | | If a user has never logged in before and they login using autologin, then we don't select the correct session type if they end up with a wayland session. This is because we fail to initialize the session type based on the default session type. This commit changes the code to update the session type anytime the session defaults are reset. https://bugzilla.gnome.org/show_bug.cgi?id=761785
* gdm-x-session: fix pointer confusion in UpdateActivationEnv callRay Strode2016-02-091-1/+1
| | | | | | commit 99eeae91c1f11997521ad3bc016a7b2d23ec7942 introduced a call to UpdateActivationEnvironment but mucked up the GVariantBuilder declaration. This commit fixes that.
* Updated Kazakh translationBaurzhan Muftakhidinov2016-02-081-67/+32
|
* Updated French translationAlexandre Franke2016-02-081-142/+35
|
* Updated Polish translationPiotr Drąg2016-02-061-45/+28
|
* Updated Slovak translationDušan Kazik2016-02-061-93/+35
|
* gdm-x-session: fix tiny leak in error pathRay Strode2016-02-051-1/+1
| | | | | | | I wasn't cleaning up the dbus connection in out: so it leaked in an error path. Spotted by Michael Catanzaro
* daemon: support dbus user buses with X sessionsRay Strode2016-02-041-3/+39
| | | | | | | | | | | | | | | | | | | If the dbus user bus was started when the user first logged in, before the session was started, then that dbus daemon won't have DISPLAY and XAUTHORITY in its activation environment. This means programs activated from that dbus daemon also won't have DISPLAY and XAUTHORITY in their activation environments. This commit changes GDM to explicitly put the two variables in the activation environment via D-Bus, rather than sending them into the bus environment process when launching the bus (since in the case of the user bus, we don't launch it). https://bugzilla.gnome.org/show_bug.cgi?id=761568
* configure: ensure wayland support is properly displayed in configure summaryFrederic Crozat2016-02-041-1/+1
| | | | | | | Wayland support status was never properly displayed in configure summary output. https://bugzilla.gnome.org/show_bug.cgi?id=760512
* Updated Brazilian Portuguese translationRafael Fontenelle2016-02-031-63/+40
|
* Updated Slovenian translationMatej Urbančič2016-02-021-47/+673
|
* Updated Spanish translationDaniel Mustieles2016-01-311-296/+43
|
* Updated Friulian translationFabio Tomat2016-01-271-186/+35
|
* configure: bump to 3.19.4.13.19.4.1Ray Strode2016-01-251-1/+1
|
* NEWS: update for releaseRay Strode2016-01-251-0/+6
|
* Updated Hungarian translationGábor Kelemen2016-01-251-161/+40
|
* session: free conversation hash when disposing sessionRay Strode2016-01-221-0/+3
| | | | | | | We're currently leaking the hash table when disposing the session, this commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=754814
* session: keep session object alive while establishing credentialsRay Strode2016-01-221-2/+5
| | | | | | | | | | | The only reference to session objects gets cleaned up when verification-complete is emitted, which happens in the middle of the establish_credentials handler. This commit makes sure the session object stays alive until the handler completes to prevent a crash. https://bugzilla.gnome.org/show_bug.cgi?id=754814
* Updated Bulgarian translationAlexander Shopov2016-01-221-58/+41
|
* configure: bump to 3.19.43.19.4Ray Strode2016-01-211-1/+1
|
* NEWS: update for releaseRay Strode2016-01-211-0/+11
|
* session-worker: drop SIGINT and rework SIGTERM handlerVasily Khoruzhick2016-01-211-12/+9
| | | | | | | | | | | | | | | | The gdm session worker sets up main loop dispatched signal handlers for SIGINT and SIGTERM. These handlers won't run if the pam module is blocking, since the main loop isn't iterating. This commit drops the SIGINT handler, and changes the SIGTERM handler to exit with a successful exit code, which gives us the same effective behavior as before but will work even if the pam module is blocked. Small changes by Ray Strode https://bugzilla.gnome.org/show_bug.cgi?id=755291
* gdm-session: emit verification-complete even for loginsRay Strode2016-01-211-8/+7
| | | | | | | | | | Right now we only emit verification-complete when the a user successfully reauthenticates. We should also do it when they successfully initially authenticate. This commit fixes that. https://bugzilla.gnome.org/show_bug.cgi?id=754814