Hallo, * Eduard Bloch [Sat, Jan 02 2021, 11:52:50AM]: > Hallo, > * Jamie Zawinski [Wed, Dec 30 2020, 07:05:29PM]: > > > created. With absolute path, it is created but then it's created by > > > lightdm user first and then maybe the user session cannot replace it. > > > > Ok, that definitely means you're running as the wrong user, which explains > > why .Xauthority is not readable. Though why the earlier xscreensaver log > > said you were running as the correct user is confusing. Unless that log was > > from before this problem began. > > I don't have enough information to judge here. What I see is that the > xscreensvaer logo appears twice, i.e. when the lightdm screen comes and > when the xsession starts. When I check on the process list briefly in > those first seconds, there is: > > lightdm 4881 0.2 0.0 18924 5936 ? Ss 11:44 0:00 \_ > xscreensaver > lightdm 4959 0.0 0.0 5716 1064 ? SN 11:44 0:00 | \_ > xscreensaver-systemd > > So not running as user. And that process is terminated soon. And what > happened with the second appearence of the logo? This looks like an > aborted start of xscreensaver. > > Is this maybe lightdm failing to stop its instance in time so > xscreensaver cannot attach the the session and silently dies? > > Maybe should be a question to Debian maintainers of resp. stakeholders. > > > > Ok. Is this supposed to be gone when user logs out? Does this interfere > > > with my trying different parameters (-log, --log, etc.) above, are those > > > cached and therefore ignored after subsequent changes?
So I switched to another DM, gdm3 instead of lightdm. And rebootet. gdm3 does not use xscreensaver, IIRC. Result: xscreensaver still not starting, nor is there a xscreensaver-systemd process. But there is: Debian-+ 7672 0.0 0.0 232856 6072 tty1 Sl+ 11:54 0:00 | \_ /usr/libexec/gsd-screensaver-proxy Which also terminates within the first minute. And like before, systemctl --user status xscreensaver.service only shows the logs which failed due to inaccessible DISPLAY and cookie problems. But that status also never changes. I can logout, and login again, there is no additonal attempt to start the user service. I can run systemctl --user restart xscreensaver.service manually and then it starts, and on logout it is reported as failed Active: failed (Result: exit-code) since Sat 2021-01-02 12:10:58 CET; 14s > Process: 6435 ExecStart=xscreensaver (code=exited, status=1/FAILURE) (obviously: xscreensaver[6435]: X connection to :0 broken) But it is NEVER RESTARTED. I think it should be answered by Debian maintainers and I don't know whom to ask: - how is the DISPLAY environment for systemd user session supposed to get there? - why are failed services not restarted when user logs out / logs in? For now, I will run in from .xsession again. systemd integration is just buggy. Best regards, Eduard.