[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: xscreensaver regressions?
On Tue, 24 Jul 2018, John D. Baker wrote:
> On Tue, 24 Jul 2018, Thomas Klausner wrote:
> > On Mon, Jul 02, 2018 at 12:04:04PM -0500, John D. Baker wrote:
> > > After updating xscreensaver, a number of display hacks no-longer work,
> > > claiming "no image loading support".
> > I think I've fixed this.
> I saw that and updated my "x11/xscreensaver" to HEAD and rebuilt the
> package. I have not yet updated it on a machine where it will be run.
> I hope to do that soon.
I've now updated on a machine that actually runs 'xscreensaver'. The
problem display hacks that claimed "no image loading support" and/or
previously dumped core no-longer do.
A few of the display hacks that expect to load images still don't actually
do. Instead, they only show the grey checkerboard "canvas". They should
at least use the "xscreensaver" logo image if they can't load anything
Still failing to load images:
A clue is that the only core file left now is "xscreensaver-get.core"
which I believe is related to image loading. It's not clear which of
the "/usr/pkg/bin/xscreensaver-getimage*" executables this matches, if
Sure enough, the timestamp on the core file coincides with the time the
most recent of the above display hacks to be run (checking via
If the display hack has a specific (set of) image(s), it loads fine.
If it expects a user-set image source (directory, screen-grab, video
frame, default xscreensaver logo image) then whatever produces that core
file dumps core.
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Main Index |
Thread Index |