commit e28c512b8af495c15fa78dff9a0e21dd95ccd33c (HEAD -> gnome-3-20, github/gnome-3-20) Author: Ray Strode Date: Mon Apr 11 11:53:32 2016 -0400 configure: bump to 3.20.1 M configure.ac commit cc6a286b3cb7caa85fb219c630ea66ddcbde1659 Author: Ray Strode Date: Mon Apr 11 11:41:49 2016 -0400 NEWS: update for release M NEWS commit e84653d1679397a897c5657880e8f96822270633 (origin/gnome-3-20) Author: Alexander Shopov Date: Sat Apr 9 07:36:41 2016 +0300 Updated Bulgarian translation M po/bg.po commit 1d532bed525262baa3d051ebbcbd07a1027fff7e Author: Fabio Tomat Date: Fri Apr 8 09:37:35 2016 +0000 Updated Friulian translation M po/fur.po commit 2d2dcf3354701aa663d08e8337c608e245a9f2c1 Author: Andreas Henriksson Date: Wed Mar 30 18:49:15 2016 +0200 main: fix starting gnome session via startx The changes related to gsm_util_setenv during 3.19.x seems to have broken starting a gnome desktop the old fashioned way, eg. via startx. The gnome.session required components has OnlyShowIn=GNOME; which disqualifies them from being started unless XDG_CURRENT_DESKTOP is also set to GNOME (by the gio utility function used to look up info). Currently gnome-session already carries code to catch the case of XDG_CURRENT_DESKTOP being unset and set it to GNOME as a fallback. Unfortunately the changes to gsm_util_setenv seems to have made it only set the values in the (dbus activated) child environment, rather than the current environment which g_desktop_app_info_get_show_in is looking at. Make the fallback code set XDG_CURRENT_DESKTOP in both current and child environment fixes it. Also move the entire hunk of code before initializing gio to prevent potential thread issues, now that is uses g_setenv. https://bugzilla.gnome.org/show_bug.cgi?id=764379 M gnome-session/main.c commit faf44253a5bbf0c2c554e74dab82b250a66ce25d Author: Daniel Korostil Date: Tue Mar 22 22:44:44 2016 +0200 Updated Ukrainian translation M po/uk.po commit 9eabb00b3065c1eb72deb10eb0adb3f9fdad1d13 (tag: 3.20.0)