Hallo,
I have created a new bug report for the issue of xscreensaver not being
properly terminated:
http://bugs.debian.org/979562
The issue with xscreensaver-systemd persists. It seems like either when
xscreensaver is killed by SIGTERM or it's aborted because another one is
active, there is a pr
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 y
On Jan 2, 2021, at 2:52 AM, Eduard Bloch wrote:
>
> 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
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
> 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 yo
Hallo,
* Jamie Zawinski [Tue, Dec 29 2020, 04:48:10PM]:
> > Once logged in, I can see some active process of xscreensaver (this is what
> > "pidof xscreensaver" tells me).
> >
> > But after some seconds, this process is gone. Why? Don't know.
>
> Dunno. Maybe it's trying to connect and timing out.
> Once logged in, I can see some active process of xscreensaver (this is what
> "pidof xscreensaver" tells me).
>
> But after some seconds, this process is gone. Why? Don't know.
Dunno. Maybe it's trying to connect and timing out. Run xscreensaver with --log
log.txt
Or if you have an old versi
Hallo,
* Jamie Zawinski [Mon, Dec 28 2020, 06:07:55PM]:
> The fact that $DISPLAY is not set at the time xscreensaver is launched is not
> a good sign. The cookie error suggests that ~/.Xauthority does not exist or
> is not readable. However you do appear to be running as yourself, not as
> "nobo
The fact that $DISPLAY is not set at the time xscreensaver is launched is not a
good sign. The cookie error suggests that ~/.Xauthority does not exist or is
not readable. However you do appear to be running as yourself, not as "nobody".
Perhaps $HOME is set to something weird? Maybe try setting
Package: xscreensaver
Version: 5.45+dfsg1-1
Severity: important
Hi,
just what the title says. I have configured xscreensaver start via
systemd user session as suggested in README.Debian. Not working now but
it has been a few weeks ago.
I am wondering about the MAGIC COOKIE problem. My startup se
10 matches
Mail list logo
