Ubuntu
gdm3 package

~ubuntu-desktop/ubuntu/+source/gdm3:upstream/3.28.x

  1. Git
  2. lp:~ubuntu-desktop/ubuntu/+source/gdm3
  3. upstream/3.28.x
Last commit made on 2018-08-14
Get this branch:
git clone -b upstream/3.28.x https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gdm3
Members of Ubuntu Desktop can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
upstream/3.28.x
Repository:
lp:~ubuntu-desktop/ubuntu/+source/gdm3

Recent commits

6144b08... by Iain Lane

New upstream version 3.28.3

feadaf9... by Ray Strode <email address hidden>

configure: bump to 3.28.3

a2761d5... by Ray Strode <email address hidden>

NEWS: update for release

10fbdd4... by Ray Strode <email address hidden>

session-worker: set PWD for user session

It's possible for the current working directory to be
a symlink. Some programs, and notably, the
get_current_dir_name() libc api use the PWD environment
variable to know the symlink being used (so they don't
use the canonical name that the symlink points to)

This commit makes sure we set PWD in that case, to
allow those programs to show the right path.

702d7b1... by Ray Strode <email address hidden>

session-worker: unblock SIGUSR1 before PAM

Right now we unblock SIGUSR1 just before starting
the session, but we should really do it before
starting the worker/PAM.

This commit fixes that and removes a useless call
to set SIGUSR1 back to the default disposition,
right before exec (which does the same thing anyway)

Closes: https://gitlab.gnome.org/GNOME/gdm/issues/399

765b306... by Ray Strode <email address hidden>

display: tie skeleton handlers to object lifetime

Right now we assume a display skeleton object won't
outlive its associated display object.

In theory that should be true, but if we accidentally
leak the skeleton it could erroneously happen.

If that does happen then we'll end accessing free'd
memory, so the leak will turn into a crasher.

This commit addresses this problem by ensuring
the skeleton signal handlers are disconnected when the
associated display object goes away.

CVE-2018-14424

6060db7... by Chris Coulson

display-store: Pass the display object rather than the id in the removed signal

By the time GdmDisplayStore emits the "display-removed" signal, the display
is no longer in the store and gdm_display_store_lookup will not work in
signal handlers.

Change the "display-removed" parameter from the display id to the GdmDisplay
object, so that signal handers can perform any cleanup they need to do

CVE-2018-14424

Closes: https://gitlab.gnome.org/GNOME/gdm/issues/401

161f346... by Pieter Schalk Schoeman <email address hidden>

Update Afrikaans translation

f2e153b... by Ray Strode

Merge branch 'cherry-pick-a913eea7' into 'gnome-3-28'

data: change cirrus blacklist to use gdm-disable-wayland

See merge request GNOME/gdm!8

a9b82ca... by Ray Strode <email address hidden>

data: change cirrus blacklist to use gdm-disable-wayland

Now that we have a gdm-disable-wayland binary for disabling
wayland at boot, we should use it.

This commit changes the cirrus udev rule to use gdm-disable-wayland,
rather than running sh and printf.

https://bugzilla.gnome.org/show_bug.cgi?id=796315

(cherry picked from commit a913eea70342411247e770a91b75dd800941bb6e)