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 sequence is
old school, lightdm -> Xsession and ~/.xsession contains a few commands
and eventually "exec icewm-session".
One noteworthy thing is also that for a few seconds after login I can
see an active xscreensaver process in the process list and then it
suddenly terminates.
$ systemctl --user status xscreensaver.service
â—? xscreensaver.service - XScreenSaver
Loaded: loaded (/usr/lib/systemd/user/xscreensaver.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-12-29 00:30:47 CET; 7min
ago
Process: 2652 ExecStart=xscreensaver (code=exited, status=1/FAILURE)
Main PID: 2652 (code=exited, status=1/FAILURE)
CPU: 6ms
Dez 29 00:30:47 whitestar xscreensaver[2652]: xscreensaver: 00:30:47: warning:
$DISPLAY is not set: defaulting to ":0.0".
Dez 29 00:30:47 whitestar xscreensaver[2652]: Invalid MIT-MAGIC-COOKIE-1
keyxscreensaver: 00:30:47: Can't open display: :0.0
Dez 29 00:30:47 whitestar xscreensaver[2652]: xscreensaver: 00:30:47: running
as bloch/bloch (500/500)
Dez 29 00:30:47 whitestar xscreensaver[2652]: xscreensaver: 00:30:47: Errors at
startup are usually authorization problems.
Dez 29 00:30:47 whitestar xscreensaver[2652]: But you're not
logging in as root (good!) so something
Dez 29 00:30:47 whitestar xscreensaver[2652]: else must be wrong.
Did you read the manual and the FAQ?
Dez 29 00:30:47 whitestar xscreensaver[2652]:
https://www.jwz.org/xscreensaver/faq.html
Dez 29 00:30:47 whitestar xscreensaver[2652]:
https://www.jwz.org/xscreensaver/man.html
Dez 29 00:30:47 whitestar systemd[2626]: xscreensaver.service: Main process
exited, code=exited, status=1/FAILURE
Dez 29 00:30:47 whitestar systemd[2626]: xscreensaver.service: Failed with
result 'exit-code'.
Best regards,
Eduard.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.1+ (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xscreensaver depends on:
ii init-system-helpers 1.60
ii libatk1.0-0 2.36.0-2
ii libc6 2.31-6
ii libcrypt1 1:4.4.17-1
ii libglib2.0-0 2.66.4-1
ii libgtk2.0-0 2.24.32-5
ii libpam0g 1.4.0-1
ii libpango-1.0-0 1.46.2-3
ii libsystemd0 247.2-3
ii libx11-6 2:1.6.12-1
ii libxext6 2:1.3.3-1.1
ii libxi6 2:1.7.10-1
ii libxinerama1 2:1.1.4-2
ii libxml2 2.9.10+dfsg-6.3+b1
ii libxmu6 2:1.1.2-2+b3
ii libxrandr2 2:1.5.1-1
ii libxt6 1:1.2.0-1
ii libxxf86vm1 1:1.1.4-1+b2
ii xscreensaver-data 5.45+dfsg1-1
Versions of packages xscreensaver recommends:
pn libjpeg-turbo-progs <none>
ii perl 5.32.0-6
ii wamerican [wordlist] 2019.10.06-1
ii wngerman [wordlist] 20161207-8
ii xfonts-100dpi 1:1.0.4+nmu1
Versions of packages xscreensaver suggests:
ii chromium [www-browser] 87.0.4280.88-0.3
ii elinks [www-browser] 0.13.2-1+b1
ii falkon [www-browser] 3.1.0+dfsg1-9
ii firefox [www-browser] 84.0-3
ii fortune-mod [fortune] 1:1.99.1-7.1
ii gdm3 3.38.2.1-1
ii lynx [www-browser] 2.9.0dev.6-1
pn qcam | streamer <none>
ii w3m [www-browser] 0.5.3-38+b1
pn xdaliclock <none>
pn xfishtank <none>
pn xscreensaver-data-extra <none>
pn xscreensaver-gl <none>
pn xscreensaver-gl-extra <none>
-- no debconf information
--
<Aquarioph> hm... kann man eigentlich auch von vorne poppen oder nur von
hinten?
--
<cpt_nemo> Wo kann man eigentlich Verbesserungen für die Fortunes anbringen?
<HE> cpt_nemo: Geschichtsfälscher!
