Passe __GL_MaxFramesAllowed=1 a cosmic-comp lorsque /proc/driver/nvidia
existe. Sans cela le pilote laisse grossir sa file de trames pre-rendues,
ce qui ajoute de la latence a l'affichage (smithay#1562, cosmic-comp#1179).
La variable n'est ajoutee que sur machine NVIDIA ; ailleurs l'environnement
transmis reste le seul COSMIC_SESSION_SOCK.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
launch-pad ne relance que les processus qui sortent en erreur: une sortie propre du demon (par ex. un pkill -x cosmic-settings qui touche aussi le demon a cause de la troncature comm a 15 caracteres) laissait la session sans service varlink audio jusqu'au logout. Le demon est desormais relance par cosmic-session tant que la session n'est pas en cours d'extinction, avec une limite de 5 relances rapprochées pour éviter une boucle sur un démon cassé.
This is needed for `cosmic-settings-daemon` to be able to use Wayland.
Required for https://github.com/pop-os/cosmic-settings-daemon/pull/153.
Though passing the env vars here seems reasonable in general, and
without that change is harmless and should have no impact.
Our "privileged sockets" support in cosmic comp has never been enforced
by default, and predates the Wayland security context protocol. That
should cover sandboxed clients, while we can't really secure against
non-sandboxed clients.
We also rely on the DBus socket-activated portal backend having access
to "privileged" protocols now.
So it makes sense to remove this.
changes for code review
[squash] systemd scopes support
(doesn't compile) zbus connection seems to be missing sync
I think I got it
scoping works again
switched to a different method of systemd detection and cleaned up dead code
switch launchpad dependency back to main and removed unused imports
