Hallo, * Michael Biebl [Sun, Jan 10 2021, 08:24:12PM]: > Am 10.01.21 um 20:02 schrieb Jamie Zawinski: > > > Why would a xscreensaver instance running for user A have any influence > > > on a xscreensaver instance running for user B? That seems absolutely > > > weird to me and something I don't understand. > > > > Yeah, that sounds impossible, assuming that the X server has restarted > > between user A and user B. > > > > If things have gone wrong in a weird way, the "xscreensaver-systemd" > > process of user A might linger, but it won't be able to communicate with > > user B's xscreensaver. > > Since Eduard has been claiming this originally: > > > - having this xscreensaver hanging around disturbs the startup of > > another xscreensaver process in the new user session > > I guess he needs to back this up somehow. > Unfortunately I haven't seen any log files or anything, which would give us > the opportunity to retrace what's happening.
Not sure which kind of backup you expect. How can I generate more useful logfiles? IMHO I asked before for some kind of tracing functionality to become able to get that information, i.e. to see how systemd is ticking, to see what is happening or how the the delayed SIGTERM is triggered. Those are basically the symptoms I see: my .icewm/startup file at the moment contains: xscreensaver -nosplash -log wtf-xscreensaver.txt & When icewm starts, I see the splash screen for a brief moment (not joking, looks -nosplash has no effect there), but it does not happen every time. And in wtf-xscreensaver.txt I find: xscreensaver: 21:50:06: already running on display :0 (window 0x400005) from process 9797 (lightdm@whitestar). Second attempt (and a different PID): When I run "xscreensaver-command -lock" (through ctrl-alt-del dialog of icewm) then the screen gets locked, and pushing a key shows me the credentials prompt for the user called "lightdm". Or, if run ps quick enough before it's killed, I see: user 3904 0.0 0.0 5712 1128 ? SN 21:13 0:00 xscreensaver-systemd -verbose lightdm 11997 0.1 0.0 18948 5952 ? Ss 21:55 0:00 xscreensaver lightdm 12068 0.0 0.0 5712 1128 ? SN 21:55 0:00 xscreensaver-systemd user 12416 0.0 0.0 3748 664 pts/0 S+ 21:56 0:00 grep saver (one of those "xscreensaver-systemd" belongs to an earlier session, this is another complaint of mine in #978589 but it's claimed not to cause the main issue). Best regards, Eduard.
