On Jun 26, 2022, at 1:59 AM, Sergio Gelato <sergio.gel...@astro.su.se> wrote: > >> The display connection that both xscreensaver and xscreensaver-systemd have >> open will close with SIGPIPE. > > This does not match my observations. xscreensaver does appear to have a > connection to the X server, but xscreensaver-systemd does not. (It seems to > have connections to DBus instead.)
Huh. Well, xscreensaver-systemd calls XOpenDisplay specifically to make this happen, and when I run xscreensaver-systemd and then kill the X server, I get this: # ./xscreensaver-systemd -v xscreensaver-systemd: 02:07:08: registered as "org.jwz.XScreenSaver" xscreensaver-systemd: 02:07:08: registered as "org.freedesktop.ScreenSaver" xscreensaver-systemd: 02:07:08: "org.gnome.SessionManager" not in use xscreensaver-systemd: 02:07:08: "org.kde.Solid.PowerManagement.PolicyAgent" not in use [ kill server ] xscreensaver-systemd: 02:07:26: X connection closed Exit 1 -- Jamie Zawinski • jwz.org • dnalounge.com
