| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 16_xserver_path.patch | Use X_PATH and related environment variables when they exist Based on a patch by Julien Cristau. |
Josselin Mouette <joss@debian.org> | no | vendor, Debian | 2010-05-07 | |
| 90_config_comments.patch | Add some comments in the daemon.conf file to explain the available options Thanks to Joey Hess. |
Josselin Mouette <joss@debian.org> | no | debian | vendor, Debian | 2016-03-15 |
| 91_dconf_database_path.patch | Point to a dconf path in /var/lib/gdm3 instead of the one in $DATADIR | Josselin Mouette <joss@debian.org> | no | vendor, Debian | 2014-05-10 | |
| 92_systemd_unit.patch | Configure systemd service for Debian * Regenerate dconf defaults from source files before start or reload * Use the right executable name for Debian * Delay restarts a little * Don't install the display-manager.service alias, which is managed jointly by all Debian display managers via a debconf question |
Debian GNOME Maintainers | no | vendor, Debian | 2017-10-05 | |
| 94_retain_xorg_log.patch | reinstate Xorg.N.log at Xorg maintainers' request | Simon McVittie <smcv@debian.org> | no | debian | vendor, Debian | 2014-11-08 |
| debian/utils-gdm-auth-config-debian-Add-debian-hook-for-gdm-conf.patch | utils/gdm-auth-config-debian: Add debian hook for gdm-config This is distro-specific configuration that gdm allows distro to configure so add the debian version for it that will be installed when -Ddistro=debian |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2024-04-04 | ||
| udev-rules-Add-check-for-nvidia-S0ix-suspend.patch | udev rules: Add check for nvidia S0ix suspend (cherry picked from commit 5a305d654ccf250f23c634cedee69a108996f5eb) |
=?utf-8?q?Jos=C3=A9_Relvas?= <josemonsantorelvas@gmail.com> | no | 2024-03-22 | ||
| manager-Move-g-i-s-chown-to-when-PAM-authentication-compl.patch | manager: Move g-i-s chown to when PAM authentication completed During the PAM conversation, `pam_gnome_keyring` will try to unlock the login keyring. If the keyring created by gnome-initial-setup hasn't changed ownership, then `gnome-initial-setup-copy-worker` can't move it in place and `gnome-keyring-daemon` will try to create a new login keyring. This either means the keyring created in g-i-s is lost or g-k-d gets confused about a keyring that shows up after initializing but before it's received the unlock/create request. Similarly, the systemd user session is started by `pam_systemd` and will trigger any number of services that might consume the config files g-i-s has created. To ensure that files are ready before any consumers have started, chown them right after the user credentials have been established but before the PAM session has been started. (cherry picked from commit ca7d30c3a953aac58976c99e26fceead3427f69b) |
Dan Nicholson <dbn@endlessos.org> | no | 2024-03-13 |