summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Updated Portuguese translationgnome-3-14Pedro Albuquerque2015-11-221-185/+162
|
* Updated Swedish translationAnders Jonsson2015-05-061-4864/+3349
|
* Updated Icelandic translationSveinn í Felli2015-04-271-3448/+295
|
* systemd: change to KillMode=process•Ray Strode2015-03-301-0/+1
| | | | | | | | | | | | By default systemd will kill the entire control-group in one fell swoop. The problem is, things don't get shutdown in the right order then, and there's a race where GDM will begin restarting X servers as soon as they're killed. This commit tells systemd to just kill the main GDM process, and let it handle killing all its children on its own. https://bugzilla.gnome.org/show_bug.cgi?id=747088
* manager: NULL unreferenced objects in disposeRay Strode2015-03-301-4/+7
| | | | | | | Now that we're using a dispose handler instead of a finalize handler, we need to make sure we nullify our objects after unrefing them. https://bugzilla.gnome.org/show_bug.cgi?id=745975
* manager: make sure to explicitly close user sessions in disposeRay Strode2015-03-301-0/+4
| | | | | | We don't want ref count leaks to lead to unkilled sessions. https://bugzilla.gnome.org/show_bug.cgi?id=745975
* manager: clean up manager in dispose not finalizeRay Strode2015-03-301-4/+4
| | | | | | Seems more appropriate. https://bugzilla.gnome.org/show_bug.cgi?id=745975
* configure: bump to 3.14.23.14.2Ray Strode2015-03-301-1/+1
|
* NEWS: update for releaseRay Strode2015-03-301-0/+10
|
* manager: don't block on plymouth quittingRay Strode2015-03-251-4/+2
| | | | | | | plymouth can quit in the background, the only thing we need to block synchronously on is it deactivating. https://bugzilla.gnome.org/show_bug.cgi?id=746498
* systemd: don't require lang file to existRay Strode2015-03-251-1/+1
| | | | | | | | | | | | | | commit fbb922cfcf4e389b0aa416d9a81c45f8f938f104 made sure to source /etc/default/locale on debian so that GDM gets started with the correct locale. Unfortunately, now if that file doesn't exist (which is entirely legitimate) then GDM won't start. This commit makes sure to still start GDM, even if the file couldn't be sourced. https://bugzilla.gnome.org/show_bug.cgi?id=745868
* systemd: make sure to only start plymouth is startedRay Strode2015-03-251-2/+14
| | | | | | | | | | | This commit makes sure gdm doesn't start in parallel with plymouth, which could lead to plymouth activating after X is started. Furthermore, GDM is replacing getty@tty1.service and plymouth-quit.service, so it needs to have the same dependencies as them. https://bugs.freedesktop.org/show_bug.cgi?id=89475
* settings: print custom.conf at startupRay Strode2015-03-251-0/+8
| | | | This makes it clear what settings gdm is using.
* systemd: import language into daemon environmentRay Strode2015-03-252-0/+3
| | | | | | | | | By default GDM is started with a pretty blank environment. This commit makes sure that the default locale for the system is used. https://bugzilla.gnome.org/show_bug.cgi?id=745286
* manager: finish displays even if they're unmanagedRay Strode2015-03-251-4/+2
| | | | | | | Some displays may be PREPARED, but not yet MANAGED. Those need to be finished at finalize time too. Fixes an assertion failure crash in some cases.
* session: plug memory leakRay Strode2015-03-251-1/+1
| | | | | | gdm_session_get_session_id erroneously strdup's it's return value. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* xdmcp-factory: handle display status changes after managerRay Strode2015-03-251-4/+4
| | | | | | | | The factory removes the display from the display store, so it should run last. Furthermore the manager, sets up the greeter session, so it should run first. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* manager: always call gdm_display_unmanage before finishRay Strode2015-03-251-0/+1
| | | | | | We need to clean up various resources before finishing the display. https://bugzilla.gnome.org/show_bug.cgi?id=744764
* correct ShowLocalGreeter (standalone XDMCP server)Maxime de Roucy2015-03-251-2/+2
| | | | | | | | Get the ShowLocalGreeter option from configuration file BEFORE launching the gdm manager. In order to let the manager know if it have to launch a local X server or not. https://bugzilla.gnome.org/show_bug.cgi?id=743440
* defaults: set default ping interval to 0Ray Strode2015-03-251-1/+1
| | | | | | | | | | We apparently never reset the ping alarm() so a non-0 ping interval means the session will unconditionally be killed after the ping interval. For now set the ping interval to 0. https://bugzilla.gnome.org/show_bug.cgi?id=741766
* worker: make sure SavedSessionNameRead is emitted for conversations without ↵Ray Strode2015-03-251-12/+21
| | | | | | | | | | | | initial username We emit SavedSessionNameRead when we know the session associated with a user account. Unfortunately, we don't emit the signal in the case we don't know the username up front (such as with a smartcard). This commit fixes it to be emitted in that case. https://bugzilla.gnome.org/show_bug.cgi?id=740139
* Updated Bosnian translationSamir Ribic2015-03-141-3765/+291
|
* systemd: call plymouth-quit if gdm failsSimon McVittie2015-03-121-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | gdm.service Conflicts with plymouth-quit.service, so it does not run when it normally would (because GDM wants to handle the handover from plymouth to X11 itself). This means that if gdm fails to start for whatever reason, plymouth is never stopped, so plymouth-quit-wait.service never finishes. This, in turn, means that getty@tty*.service, which is After plymouth-wait-quit.service, never starts, and there is no way to log in locally and fix the problem (Debian bug #780257, but not Debian-specific). In Debian 8, not all display managers have been migrated to participate in managing the display-manager.service symlink yet (in particular, kdm and wdm have not), so gdm has a transitional ExecStartPre that stops it from running if kdm or wdm is selected as the active DM. This has the same effect of preventing plymouth from running (Debian-specific bug #766462). It's easy to avoid both of those situations by scheduling plymouth-quit.service to run if gdm fails. Bug: https://bugzilla.gnome.org/show_bug.cgi?id=746023 Bug-Debian: https://bugs.debian.org/766462 Bug-Debian: https://bugs.debian.org/780257
* launch-environment: Propagate XCURSOR_PATH and XDG_CONFIG_DIRSLuca Bruno2014-11-291-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=740632
* Update Uzbek@cyrillic translationBahodir Mansurov2014-11-011-812/+328
|
* configure: bump to 3.14.13.14.1Ray Strode2014-10-141-1/+1
|
* NEWS: update for releaseRay Strode2014-10-141-0/+9
|
* redhat-pam: get rid of pam_nologin from launch environment stackRay Strode2014-10-101-1/+0
| | | | | pam_nologin is supposed to prevent users from logging in, not prevent the login screen from coming up.
* Don't leak result of g_dbus_connection_new_for_address_finish()Owen W. Taylor2014-10-091-5/+10
| | | | | | | | g_dbus_connection_new_for_address_finish() returns a new reference; we can't simply ignore the returned connection, even though it is also passed in as the source object of the GAsyncReadyCallback. https://bugzilla.gnome.org/show_bug.cgi?id=738246
* Unref result of g_async_result_get_source_object()Owen W. Taylor2014-10-091-0/+3
| | | | | | | g_async_result_get_source_object() returns a reference that must be unreferenced. https://bugzilla.gnome.org/show_bug.cgi?id=738246
* Unref async results after calling g_simple_async_result_complete_in_idle()Owen W. Taylor2014-10-091-0/+26
| | | | | | | All async results were leaked, since g_simple_async_result_complete_in_idle() takes a new reference rather than assuming the ref passed in. https://bugzilla.gnome.org/show_bug.cgi?id=738246
* Update .gitignoreJasper St. Pierre2014-10-011-2/+0
|
* Remove files related to the simple-greeter and the fallback sessionLaurent Bigonville2014-10-019-75/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=710847
* daemon: don't allow worker manager interface to be unexported more than onceRay Strode2014-09-301-0/+1
| | | | | | | | | | if a conversation is stopped asynchronously and then synchronously, we will end up trying to unexport the bus interface more than once, leading to log spew. This commit protects against that. https://bugzilla.gnome.org/show_bug.cgi?id=737391
* Updated Bengali (India) translationSaibal Ray2014-09-261-519/+399
|
* Updated translation for Afrikaans (af)Friedel Wolff2014-09-231-535/+412
|
* Updated Scottish Gaelic translationGNOME Translation Robot2014-09-231-29/+58
|
* configure: bump to 3.14.03.14.0Ray Strode2014-09-221-1/+1
|
* NEWS: update for releaseRay Strode2014-09-221-0/+5
|
* Updated Hindi translationRajesh Ranjan2014-09-221-521/+395
|
* Updated Greek translationMaria Mavridou2014-09-211-504/+130
|
* Updated Nepali translationPawan Chitrakar2014-09-191-58/+48
|
* Updated Nepali translationPawan Chitrakar2014-09-171-73/+64
|
* Updated Malay translationUmarzuki Bin Mochlis Moktar2014-09-171-3370/+2534
|
* configure: bump to 3.13.923.13.92Ray Strode2014-09-171-1/+1
|
* NEWS: update for releaseRay Strode2014-09-171-0/+7
|
* Update caribou autostart file for caribou path changesKalev Lember2014-09-173-2/+14
| | | | | | The executable was moved from bin to libexec in caribou 0.14.4 release. https://bugzilla.gnome.org/show_bug.cgi?id=736612
* daemon: use g_clear_object to reduce clutterRay Strode2014-09-161-4/+2
|
* Updated Bengali (India) translationSaibal Ray2014-09-161-609/+159
|
* Updated Nepali translationPawan Chitrakar2014-09-131-3432/+2574
|
View Lorry Controller Status