Re: x11/xscreensaver 2026Q1 locks and no login

[snow flurry <snow%flurry.sh@localhost>]

On Tuesday, October 6, 2026 10:45:37 AM Pacific Daylight Time Ramiro 
Aceves wrote:
> El 6/10/26 a las 9:08, Martin Husemann escribió:
> > On Tue, Oct 06, 2026 at 09:01:01AM +0200, Ramiro Aceves wrote:
> >> bsod.c:5357:17: warning: array subscript has type 'char'
> >> [-Wchar-subscripts]>> 
> >>   5357 |     if (isalpha(*s)) *s = toupper (*s);
> >>   
> >>        |                 ^
> >> 
> >> bsod.c:5357:36: warning: array subscript has type 'char'
> >> [-Wchar-subscripts]>> 
> >>   5357 |     if (isalpha(*s)) *s = toupper (*s);
> >>   
> >>        |                                    ^
> >> 
> >> bsod.c:5373:19: warning: array subscript has type 'char'
> >> [-Wchar-subscripts]>> 
> >>   5373 |       if (isalpha(*s)) *s = toupper (*s);
> >>   
> >>        |                   ^
> >> 
> >> bsod.c:5373:38: warning: array subscript has type 'char'
> >> [-Wchar-subscripts]>> 
> >>   5373 |       if (isalpha(*s)) *s = toupper (*s);
> >> 
> >> (this is an example of compiling xscreensaver un mi RPi4, just to
> >> show it)> 
> > This are all clearly bugs and easily fixable.
> > 
> > Just the full log of this type of warning is enough to fix it, you
> > don't need a crash dump.
> > 
> > To get a crash dump you can add this:
> > 
> > kern.coredump.setid.dump=1
> > 
> > to /etc/sysctl.conf. The dump will be saved in /var/crash/ by
> > default.
> > 
> > Martin
> 
> Thanks Martin for the tip.
> 
> I think I did sysctl -w kern.coredump.setid.dump=1 "on the fly" and
> did not get the crash dump in /var/crash. Is it equivalent doing it
> that way  or should it be configured in /etc/sysctl.conf.

xscreensaver drops almost immediately to the running user's ID, so it 
might not be able to write to /var/crash. Do you get a crash dump if you 
temporarily set kern.coredump.setid.path to something writable by your 
user? Like this:

kern.coredump.setid.path=/tmp/%n.core

> Regards.
> Ramiro.


-- 
snow flurry <snow%flurry.sh@localhost>