Package: mate-session-manager / 1.26.0-1+deb12u1
Metadata
| Package | Version | Patches format |
|---|---|---|
| mate-session-manager | 1.26.0-1+deb12u1 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| 0005_lock session before user switch.patch | (download) |
mate-session/gsm-manager.c |
13 13 + 0 - 0 ! |
--- |
| 0006_util Blacklist some session specific variables.patch | (download) |
mate-session/gsm-util.c |
17 16 + 1 - 0 ! |
[patch] util: blacklist some session-specific variables Things like XDG_SESSION_ID should not be uploaded to the environment. For example this is broken currently: 1. SSH to your machine 2. Log in to MATE Shell 3. Log out 4. Log in again 5. Lock the screen 6. Try to unlock You can't, and this is because the XDG_SESSION_ID from the first session (step 2) has leaked through to the second one (step 4), and so MATE Shell is listening to the `logind` `UnlockSession` signal for the wrong session. The SSH session established in step 1 serves to keep the `systemd --user` instance alive, so that the state is not torn down between logins. Original patch for GNOME by Iain Lane <iainl@gnome.org>. Patch ported over to MATE's session manager by Mike Gabriel <sunweaver@debian.org>. |
| 0007_Fix memory leaks 284.patch | (download) |
tools/mate-session-check-accelerated-gl-helper.c |
1 1 + 0 - 0 ! |
[patch 1/2] fix memory leaks (#284) Signed-off-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de> |
| 0008_mate session fix memory leak.patch | (download) |
mate-session/gsm-manager.c |
8 6 + 2 - 0 ! |
[patch 2/2] mate-session: fix memory leak Signed-off-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de> |
| 0009_main fix double free on gl_renderer.patch | (download) |
mate-session/main.c |
1 0 + 1 - 0 ! |
[patch] main: fix double free on gl_renderer
Fixes: 1263384 ("mate-session: fix memory leak")
Fixes: #304
Signed-off-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
|
