Bug#932837: xscreensaver: No text on lock screen
> I find it strange, if I read it correctly, that it first succeeds > to replace the -*-helvetica-bold-r-*-*-*-140-*-*-*-*-iso8859-1 font > (with -*-*-medium-r-*-*-*-140-*-*-p-*-iso10646-1) twice but fails the > third time… I think the output is still truncated on that third attempt. It should end with either a line saying "substituted" or saying "unable to find any alternatives". If you run with -no-capture-stderr that should stop the truncations, hopefully. However, I thought you said that things were working ok with the self-compiled version, and it was the package-installed version where the fonts were blank? Do these commands return usable fonts? These are the fallback font patterns that it tried as a last resort, since your system has *none* of the other standard X11 fonts installed: xlsfonts -fn "-*-*-medium-r-*-*-*-140-*-*-p-*-iso10646-1" xlsfonts -fn "-*-*-medium-r-*-*-*-180-*-*-p-*-iso10646-1" Maybe test with "xterm -font " -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#932837: xscreensaver: No text on lock screen
Hello,
On Wed, Aug 19, 2020 at 11:42:55PM +0200, Nicolas Boullis wrote:
>
> On Sun, Aug 16, 2020 at 09:58:04AM -0700, Jamie Zawinski wrote:
> >
> > If you're feeling adventurous, rebuilding with DEBUG defined in
> > utils/font-retry.c and sending me the output of a run with that version
> > might be helpful. Though I guess that if the self-compiled version does not
> > exhibit the problem, that won't help.
>
> I just gave it a try. Th corresponding log is attached.
> But I guess you won’t be happy with the “<< stderr diagnostics have been
> truncated >>” part… :-/
For what it’s worth, I just tried again, after patching driver/stderr.c
to enlarge stderr_buffer (to 128kB).
The corresponding log is attached. It is not truncated.
I find it strange, if I read it correctly, that it first succeeds
to replace the -*-helvetica-bold-r-*-*-*-140-*-*-*-*-iso8859-1 font
(with -*-*-medium-r-*-*-*-140-*-*-p-*-iso10646-1) twice but fails the
third time…
Cheers,
--
Nicolas Boullis
##
xscreensaver: 14:42:29: logging to "/tmp/xscreensaver.log" at Sun Aug 23
14:42:29 2020
##
xscreensaver 5.42, copyright (c) 1991-2018 by Jamie Zawinski .
xscreensaver: 14:42:29: running as nboullis/nboullis (1000/1000)
xscreensaver: 14:42:29: in process 12878.
xscreensaver: 14:42:29: running on display ":0"
xscreensaver: 14:42:29: vendor is The X.Org Foundation, 12004000.
xscreensaver: 14:42:29: useful extensions:
xscreensaver: 14:42:29: MIT Screen-Saver (disabled at compile time)
xscreensaver: 14:42:29: Shared Memory (1.2)
xscreensaver: 14:42:29: Double-Buffering (1.0)
xscreensaver: 14:42:29: Power Management (1.1)
xscreensaver: 14:42:29: GLX
xscreensaver: 14:42:29: XF86 Video-Mode (2.2)
xscreensaver: 14:42:29: XC Misc (disabled at compile time)
xscreensaver: 14:42:29: Xinerama (1.1)
xscreensaver: 14:42:29: Resize-and-Rotate (1.5)
xscreensaver: 14:42:29: XInput
xscreensaver: 14:42:29: screen 0 non-colormapped depths: 24.
xscreensaver: 14:42:29: WARNING: RANDR and Xinerama report different
xscreensaver: 14:42:29: screen layouts! Believing RANDR.
xscreensaver: 14:42:29: screens in use: 1
xscreensaver: 14:42:29:0/0: 1366x768+0+0 (eDP-1)
xscreensaver: 14:42:29: rejected screens: 2
xscreensaver: 14:42:29:1/0: 1366x768+0+0 (HDMI-1) -- output disabled
xscreensaver: 14:42:29:2/0: 1366x768+0+0 (DP-1) -- output disabled
xscreensaver: 14:42:29: selecting RANDR events
xscreensaver: 14:42:29: not using XInputExtension.
xscreensaver: 14:42:29: consulting /proc/interrupts for keyboard activity.
xscreensaver: 14:42:29: 0: visual 0x21 (TrueColor, depth: 24, cmap: default)
xscreensaver: 14:42:29: 0: saver window is 0x41.
xscreensaver: 14:42:29: selecting events on extant windows... done.
xscreensaver: 14:42:29: awaiting idleness.
xscreensaver: 14:42:34: LOCK ClientMessage received; activating and locking.
xscreensaver: 14:42:34: 0: locked mode switching.
xscreensaver: 14:42:34: user is idle (ClientMessage)
xscreensaver: 14:42:34: blanking screen at Sun Aug 23 14:42:34 2020.
xscreensaver: 14:42:34: 0: grabbing keyboard on 0x176... GrabSuccess.
xscreensaver: 14:42:34: 0: grabbing mouse on 0x176... GrabSuccess.
xscreensaver: 14:42:34: fading...
xscreensaver: 14:42:36: fading done.
xscreensaver: 14:42:39: user is active (keyboard activity)
xscreensaver: 14:42:39: pam_start ("xscreensaver", "nboullis", ...) ==> 0
(Success)
xscreensaver: 14:42:39: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 14:42:39: pam_authenticate (...) ...
xscreensaver: 14:42:39: pam_conversation (ECHO_OFF="Password: ") ...
xscreensaver: failed -*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-180-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-170-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-160-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-150-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-140-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-130-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-120-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-110-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-100-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-90-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-80-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-70-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-60-*-*-p-*-iso10646-1
xscreensaver: trying -*-arial-bold-r-*-*-*-180-*-*-p-*-iso10646-1
xscreensaver: trying -*-arial-bold-r-*-*-*-170-*-*-p-*-iso10646-1
xscreensaver: trying -*-arial-bold-r-*-*-*-160-*-*-p-*-iso10646-1
xscreensaver: trying -*-arial-bold-r-*-*-*-150-*-*-p-*-iso10646-1
Bug#932837: xscreensaver: No text on lock screen
Hi,
On Sun, Aug 16, 2020 at 11:04:55AM -0700, Jamie Zawinski wrote:
>
> I assure you, I did not write all that code for shits and giggles, but
> to fix an actual problem people were experiencing on font-bereft
> systems like yours.
I did not pretend you wrote any code for no good reason. To be honnest,
I did not really look at the code of xscreensaver, only used it.
> Well, that set of fonts is, in fact, garbage, but I think it should
> have fallen back to
> -misc-fixed-medium-r-normal-*-*-*-*-*-c-*-iso10646-1
I know close to nothing about how fonts are managed on my system, but
I’m still curious why you consider “my” set of fonts garbage…
On Sun, Aug 16, 2020 at 09:58:04AM -0700, Jamie Zawinski wrote:
>
> If you're feeling adventurous, rebuilding with DEBUG defined in
> utils/font-retry.c and sending me the output of a run with that version might
> be helpful. Though I guess that if the self-compiled version does not exhibit
> the problem, that won't help.
I just gave it a try. Th corresponding log is attached.
But I guess you won’t be happy with the “<< stderr diagnostics have been
truncated >>” part… :-/
Anyway, I still read the line going from
xscreensaver: trying -*-bitstream vera
sans-bold-r-*-*-*-180-*-*-p-*-iso10646-1
to
xscreensaver: trying -*-bitstream vera sans-bold-r-*-*-*-60-*-*-p-*-iso10646-1
I am somewhat surprised since I do have the ttf-bitstream-vera package
installed on my system… Does it mean I’m missing something to make that
font available to xscreensaver?
Sorry if that question sounds stupid, but I wrote above that I know
close to nothing about how fonts are managed…
Regards,
--
Nicolas Boullis
##
xscreensaver: 23:25:28: logging to "/tmp/xscreensaver.log" at Wed Aug 19
23:25:28 2020
##
xscreensaver 5.42, copyright (c) 1991-2018 by Jamie Zawinski .
xscreensaver: 23:25:28: running as nboullis/nboullis (1000/1000)
xscreensaver: 23:25:28: in process 22982.
xscreensaver: 23:25:28: running on display ":0"
xscreensaver: 23:25:28: vendor is The X.Org Foundation, 12004000.
xscreensaver: 23:25:28: useful extensions:
xscreensaver: 23:25:28: MIT Screen-Saver (disabled at compile time)
xscreensaver: 23:25:28: Shared Memory (1.2)
xscreensaver: 23:25:28: Double-Buffering (1.0)
xscreensaver: 23:25:28: Power Management (1.1)
xscreensaver: 23:25:28: GLX
xscreensaver: 23:25:28: XF86 Video-Mode (2.2)
xscreensaver: 23:25:28: XC Misc (disabled at compile time)
xscreensaver: 23:25:28: Xinerama (1.1)
xscreensaver: 23:25:28: Resize-and-Rotate (1.5)
xscreensaver: 23:25:28: XInput
xscreensaver: 23:25:28: screen 0 non-colormapped depths: 24.
xscreensaver: 23:25:28: WARNING: RANDR and Xinerama report different
xscreensaver: 23:25:28: screen layouts! Believing RANDR.
xscreensaver: 23:25:28: screens in use: 1
xscreensaver: 23:25:28:0/0: 1366x768+0+0 (eDP-1)
xscreensaver: 23:25:28: rejected screens: 2
xscreensaver: 23:25:28:1/0: 1366x768+0+0 (HDMI-1) -- output disabled
xscreensaver: 23:25:28:2/0: 1366x768+0+0 (DP-1) -- output disabled
xscreensaver: 23:25:28: selecting RANDR events
xscreensaver: 23:25:28: not using XInputExtension.
xscreensaver: 23:25:28: consulting /proc/interrupts for keyboard activity.
xscreensaver: 23:25:28: 0: visual 0x21 (TrueColor, depth: 24, cmap: default)
xscreensaver: 23:25:28: 0: saver window is 0x41.
xscreensaver: 23:25:28: selecting events on extant windows... done.
xscreensaver: 23:25:28: awaiting idleness.
xscreensaver: 23:25:36: LOCK ClientMessage received; activating and locking.
xscreensaver: 23:25:36: 0: locked mode switching.
xscreensaver: 23:25:36: user is idle (ClientMessage)
xscreensaver: 23:25:36: blanking screen at Wed Aug 19 23:25:36 2020.
xscreensaver: 23:25:36: 0: grabbing keyboard on 0x176... GrabSuccess.
xscreensaver: 23:25:36: 0: grabbing mouse on 0x176... GrabSuccess.
xscreensaver: 23:25:36: fading...
xscreensaver: 23:25:38: fading done.
xscreensaver: 23:25:44: user is active (keyboard activity)
xscreensaver: 23:25:44: pam_start ("xscreensaver", "nboullis", ...) ==> 0
(Success)
xscreensaver: 23:25:44: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 23:25:44: pam_authenticate (...) ...
xscreensaver: 23:25:44: pam_conversation (ECHO_OFF="Password: ") ...
xscreensaver: failed -*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-180-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-170-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-160-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-150-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-140-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-130-*-*-p-*-iso10646-1
xscreensaver: trying -*-helvetica-bold-r-*-*-*-120-*-*-p-*-iso10646-1
Bug#932837: xscreensaver: No text on lock screen
> Well, that “set of garbage fonts” is fine for XScreenSaver 5.36… I assure you, I did not write all that code for shits and giggles, but to fix an actual problem people were experiencing on font-bereft systems like yours. >> so it would be helpful if you send me the output of xlsfonts on your >> system where it's doing something terrible. > > Here it is. Well, that set of fonts is, in fact, garbage, but I think it should have fallen back to -misc-fixed-medium-r-normal-*-*-*-*-*-c-*-iso10646-1 -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#932837: xscreensaver: No text on lock screen
Hello, On Sun, Aug 16, 2020 at 09:58:04AM -0700, Jamie Zawinski wrote: > XScreenSaver (as of 5.42) tries really hard to do something sensible > with whatever set of garbage fonts you happen to have installed, Well, that “set of garbage fonts” is fine for XScreenSaver 5.36… > so it would be helpful if you send me the output of xlsfonts on your > system where it's doing something terrible. Here it is. > Is there anything about fonts in the log output of xscreensaver > -verbose -log log.txt ? Just gave it a try. The log is attached, but I see nothing font-related. > If you're feeling adventurous, rebuilding with DEBUG defined in > utils/font-retry.c and sending me the output of a run with that > version might be helpful. Though I guess that if the self-compiled > version does not exhibit the problem, that won't help. Ok, I’ll give it a try ASAP. Cheers, -- Nicolas Boullis -arabic-newspaper-medium-r-normal--0-0-100-100-p-0-iso10646-1 -arabic-newspaper-medium-r-normal--32-246-100-100-p-137-iso10646-1 -daewoo-gothic-medium-r-normal--0-0-100-100-c-0-ksc5601.1987-0 -daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0 -daewoo-mincho-medium-r-normal--0-0-100-100-c-0-ksc5601.1987-0 -daewoo-mincho-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0 -daewoo-mincho-medium-r-normal--24-170-100-100-c-240-ksc5601.1987-0 -isas-fangsong ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 -jis-fixed-medium-r-normal--0-0-75-75-c-0-jisx0208.1983-0 -jis-fixed-medium-r-normal--16-110-100-100-c-160-jisx0208.1983-0 -jis-fixed-medium-r-normal--16-150-75-75-c-160-jisx0208.1983-0 -jis-fixed-medium-r-normal--24-170-100-100-c-240-jisx0208.1983-0 -jis-fixed-medium-r-normal--24-230-75-75-c-240-jisx0208.1983-0 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso10646-1 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-1 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-10 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-13 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-14 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-15 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-16 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-2 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-3 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-4 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-5 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-7 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-8 -misc-fixed-bold-r-normal--0-0-100-100-c-0-iso8859-9 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso10646-1 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-1 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-10 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-11 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-13 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-14 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-15 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-16 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-2 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-3 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-4 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-5 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-7 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-8 -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso8859-9 -misc-fixed-bold-r-normal--13-100-100-100-c-70-iso8859-1 -misc-fixed-bold-r-normal--13-100-100-100-c-80-iso8859-1 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso10646-1 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-1 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-10 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-11 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-13 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-14 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-15 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-16 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-2 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-3 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-4 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-5 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-7 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-8 -misc-fixed-bold-r-normal--13-120-75-75-c-70-iso8859-9 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso10646-1 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-1 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-10 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-13 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-14 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-15 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-16 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-2 -misc-fixed-bold-r-normal--13-120-75-75-c-80-iso8859-3
Bug#932837: xscreensaver: No text on lock screen
XScreenSaver (as of 5.42) tries really hard to do something sensible with whatever set of garbage fonts you happen to have installed, so it would be helpful if you send me the output of xlsfonts on your system where it's doing something terrible. Is there anything about fonts in the log output of xscreensaver -verbose -log log.txt ? If you're feeling adventurous, rebuilding with DEBUG defined in utils/font-retry.c and sending me the output of a run with that version might be helpful. Though I guess that if the self-compiled version does not exhibit the problem, that won't help.
Bug#932837: xscreensaver: No text on lock screen
Package: xscreensaver Version: 5.42+dfsg1-1 Followup-For: Bug #932837 Dear Maintainer, For what it’s worth, I just upgraded my laptop from stretch to buster and started experiencing exactly the same problem as Jacob Adams. Here is a screenshot that show the unlock dialog. I tried to downgrade xscreensaver back to the version in stretch (5.36-1) and the texts in the unlock dialog came back. I upgraded again to the version in buster (5.42+dfsg1-1) and the texts disappeared again. Hence, I don’t think it is related to the kernel or X server in use. My guess would be a missing dependency, but I don’t know what… A font? Cheers, -- Nicolas Boullis -- System Information: Debian Release: 10.5 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-10-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xscreensaver depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglade2-0 1:2.6.4-2+b1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libice6 2:1.0.9-2 ii libpam0g 1.3.1-5 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-01.42.4-8~deb10u1 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxi6 2:1.7.9-1 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmu6 2:1.1.2-2+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxt6 1:1.1.5-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 ii xscreensaver-data5.42+dfsg1-1 Versions of packages xscreensaver recommends: ii libjpeg-turbo-progs 1:1.5.2-2+b1 pn miscfiles | wordlist ii perl 5.28.1-6+deb10u1 Versions of packages xscreensaver suggests: ii firefox-esr [www-browser] 68.11.0esr-1~deb10u1 pn fortune pn gdm3 | kdm-gdmcompat pn qcam | streamer ii w3m [www-browser] 0.5.3-37 pn xdaliclock pn xfishtank pn xscreensaver-data-extra pn xscreensaver-gl pn xscreensaver-gl-extra -- no debconf information signature.asc Description: PGP signature
Bug#932837: xscreensaver: No text on lock screen
On 7/29/19 6:55 PM, Tormod Volden wrote: >> Kernel taint flags: TAINT_USER > > BTW, do you know why your kernel is tainted? I have no idea. It seems like TAINT_USER is really generic, so I'm not sure how I would track it down. > >>> If you really think its a kernel problem then I can certainly build a newer >>> version to test, but I don't currently have the time and there's nothing >>> newer >>> available from Debian AFAIK, not even in unstable. >> >> Forgot about experimental. Pulled 5.0.2-1~exp1 from there but the problem >> persists. > > I was actually thinking more of trying a really old kernel, to see if > this is a kernel regression :) They happen, especially for graphics > drivers on older hardware. But since you tried with vesa I am not > sure. Still, the intel drm will be loaded at boot and control the card > interaction. Can you try to boot with nomodeset kernel option? Not > sure what that option leaves you nowadays but maybe worth a try. can't even get X to launch with nomodeset unfortunately. > > Also if you could attach Xorg.0.log and dmesg output they may provide > some useful information. I've attached both, from right after I have locked and then unlocked the screen with xscreensaver. Hope this helps, Jacob [ 6.439] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [ 6.439] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian [ 6.439] Current Operating System: Linux lovelace 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) x86_64 [ 6.439] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=d4d53c53-7813-4738-a6d4-50266a0f2e2c ro quiet [ 6.440] Build Date: 05 March 2019 08:11:12PM [ 6.440] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [ 6.440] Current version of pixman: 0.36.0 [ 6.440] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 6.440] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 6.440] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 17:43:39 2019 [ 6.443] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 6.443] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 6.445] (==) No Layout section. Using the first Screen section. [ 6.445] (==) No screen section available. Using defaults. [ 6.445] (**) |-->Screen "Default Screen Section" (0) [ 6.445] (**) | |-->Monitor "" [ 6.446] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 6.447] (**) | |-->Device "Intel Graphics" [ 6.447] (**) | |-->GPUDevice "Intel Graphics" [ 6.447] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 6.447] (==) Automatically adding devices [ 6.447] (==) Automatically enabling devices [ 6.447] (==) Automatically adding GPU devices [ 6.447] (==) Max clients allowed: 256, resource mask: 0x1f [ 6.447] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 6.447] Entry deleted from font path. [ 6.448] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 6.448] Entry deleted from font path. [ 6.448] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 6.448] Entry deleted from font path. [ 6.448] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 6.448] Entry deleted from font path. [ 6.448] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 6.448] Entry deleted from font path. [ 6.448] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 6.448] (==) ModulePath set to "/usr/lib/xorg/modules" [ 6.448] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 6.448] (II) Loader magic: 0x559c1735be20 [ 6.448] (II) Module ABI versions: [ 6.448] X.Org ANSI C Emulation: 0.4 [ 6.448] X.Org Video Driver: 24.0 [ 6.448] X.Org XInput driver : 24.1 [ 6.448] X.Org Server Extension : 10.0 [ 6.450] (++) using VT number 7 [ 6.450] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 6.452] (II) xfree86: Adding drm device (/dev/dri/card0) [ 6.468] (--) PCI:*(0@0:2:0) 8086:5916:17aa:224f rev 2, Mem @ 0xeb00/16777216, 0x6000/268435456, I/O @ 0xe000/64, BIOS @ 0x/131072 [ 6.468] (II) LoadModule: "glx" [ 6.470] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 6.476] (II) Module glx: vendor="X.Org Foundation" [ 6.476] compiled for 1.20.4, module version = 1.0.0 [ 6.476] ABI class: X.Org Server Extension, version 10.0 [
Bug#932837: xscreensaver: No text on lock screen
> Kernel taint flags: TAINT_USER BTW, do you know why your kernel is tainted? > > If you really think its a kernel problem then I can certainly build a newer > > version to test, but I don't currently have the time and there's nothing > > newer > > available from Debian AFAIK, not even in unstable. > > Forgot about experimental. Pulled 5.0.2-1~exp1 from there but the problem > persists. I was actually thinking more of trying a really old kernel, to see if this is a kernel regression :) They happen, especially for graphics drivers on older hardware. But since you tried with vesa I am not sure. Still, the intel drm will be loaded at boot and control the card interaction. Can you try to boot with nomodeset kernel option? Not sure what that option leaves you nowadays but maybe worth a try. Also if you could attach Xorg.0.log and dmesg output they may provide some useful information. Tormod
Bug#932837: xscreensaver: No text on lock screen
On 7/29/19 1:56 PM, Jacob Adams wrote: > If you really think its a kernel problem then I can certainly build a newer > version to test, but I don't currently have the time and there's nothing newer > available from Debian AFAIK, not even in unstable. Forgot about experimental. Pulled 5.0.2-1~exp1 from there but the problem persists.
Bug#932837: xscreensaver: No text on lock screen
On 7/29/19 9:18 AM, Tormod Volden wrote: > On Tue, Jul 23, 2019 at 9:33 PM Jacob Adams wrote: >> >> No text at all appears in the unlock dialog. >> The version number and the text in the buttons simply is not visible. > > Hi Jacob, > > Thanks for your bug report. Can you please try to check if it is > related to the graphics driver? Can you try a different kernel, or use > another graphic driver? Digging around in relevant config files I found these in xorg.conf.d: /etc/X11/xorg.conf.d/10-backlight.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "Backlight" "intel_backlight" EndSection /etc/X11/xorg.conf.d/20-dri3.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" Option "DRI" "3" EndSection /etc/X11/xorg.conf.d/90-xpra-virtual.conf # Ignore all xpra virtual devices by default, # these will be enabled explicitly when needed. Section "InputClass" Identifier "xpra-virtual-device" MatchProduct "Xpra" Option "Ignore" "true" EndSection I suspect it could be 20-dri3.conf causing issues though I have switched it to just vesa, i.e. Section "Device" Identifier "Intel Graphics" Driver "vesa" #Option "AccelMethod" "sna" #Option "TearFree" "true" #Option "DRI" "3" EndSection That didn't change anything unfortunately, and neither did removing the file completely. I tested these changes by restarting my display manager after each one, i.e. systemctl restart lightdm In terms of kernel, I'm currently running linux 4.19.37-5+deb10u1 The only other kernel I have installed currently is 4.19.0-0.bpo.5, which is pretty much the same kernel. However, for completeness I tested it too, but encountered the same problem. If you really think its a kernel problem then I can certainly build a newer version to test, but I don't currently have the time and there's nothing newer available from Debian AFAIK, not even in unstable.
Bug#932837: xscreensaver: No text on lock screen
On Tue, Jul 23, 2019 at 9:33 PM Jacob Adams wrote: > > No text at all appears in the unlock dialog. > The version number and the text in the buttons simply is not visible. Hi Jacob, Thanks for your bug report. Can you please try to check if it is related to the graphics driver? Can you try a different kernel, or use another graphic driver? Regards, Tormod
Bug#932837: xscreensaver: No text on lock screen
Package: xscreensaver Version: 5.42+dfsg1-1 Severity: normal No text at all appears in the unlock dialog. The version number and the text in the buttons simply is not visible. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xscreensaver depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglade2-0 1:2.6.4-2+b1 ii libglib2.0-0 2.58.3-2 ii libgtk2.0-0 2.24.32-3 ii libice6 2:1.0.9-2 ii libpam0g 1.3.1-5 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-01.42.4-6 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxi6 2:1.7.9-1 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmu6 2:1.1.2-2+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxt6 1:1.1.5-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 ii xscreensaver-data5.42+dfsg1-1 Versions of packages xscreensaver recommends: ii libjpeg-turbo-progs 1:1.5.2-2+b1 ii perl 5.28.1-6 ii wamerican [wordlist] 2018.04.16-1 Versions of packages xscreensaver suggests: ii chromium [www-browser] 73.0.3683.75-1 ii firefox-esr [www-browser] 60.8.0esr-1~deb10u1 pn fortune pn gdm3 | kdm-gdmcompat pn qcam | streamer ii w3m [www-browser] 0.5.3-37 pn xdaliclock pn xfishtank pn xscreensaver-data-extra pn xscreensaver-gl pn xscreensaver-gl-extra -- no debconf information
