[SOLVED] Error message when starting desktop JWZ Screensaver package too old.

The GNUinator · 08-01-2014, 11:06 AM

Got a nasty error message that distro is not doing me a favor if they packaged such an old version of xscreensaver. Error message says to build from source. Yet, when one goes to www.jwz.org/ to look for source, the message is numerous dependencies, use package binaries. This error message has just started today. Anyone else seen it? My desktop is xfce4, and am running Slackware 14.1 x86_64.
my .Xdefaults
-------------cut here -------------
XTerm*faceName: Droid Sans Mono
XTerm*faceSize: 10
XTerm*cursorBlink: true
XTerm*saveLines: 32768
XTerm*locale: true

! Xft.antialias: 1
Xft.dpi: 96
Xft.antialias: 1
Xft.hinting: 1
Xft.hintstyle: hintfull
Xft.lcdfilter: lcddefault
Xft.rgba: rgb

URxvt.font: xft

roid Sans Mono

ixelsize=13
URxvt.saveLines: 65535
URxvt.scrollBar: false
URxvt.reverseVideo: true
URxvt.depth: 32
URxvt.foreground: rgba:0000/0000/0000/cccc
URxvt.background: white
Rxvt.cursorBlink: true
Rxvt.visualBell: true
----------------end cut --------------

keefaz · 08-01-2014, 11:55 AM

Hey, I had the same issue

Just go to your favorite Slackware mirror, find slackware64-14.1/source/xap/xscreensaver
and download the various package files, download xscreensaver sources from www.jwz.org in the same directory, chmod +x then execute ./xscreensaver.Slackbuild as root and build and upgradepkg xscreensaver

Not even need to modify the slackbuild script to change version, it's done automatically
I didn't notice any dependency issue

ljb643 · 08-01-2014, 11:59 AM

It has a 12 month trigger (July 2013 version date, 12 months later August 1st it starts complaining). We have 5.22, latest is 5.29, so it should be upgraded. It would be nice if a Slackware patch appeared...

keefaz · 08-01-2014, 12:01 PM

I must admit it's weird programm behaviour complaining that it's one year old so it's nasty while bad talking about the distro packagers wtf

ljb643 · 08-01-2014, 12:20 PM

Quote:

Originally Posted by keefaz

I must admit it's weird programm behaviour complaining that it's one year old so it's nasty while bad talking about the distro packagers wtf

From the programmer (comments in the code where it does the date check):

Quote:

Getting very tired of bug reports of already-fixed bugs due to Linux distros shipping multi-year-old versions

(I guess "multi-year-old" means more than 1 year old)

keefaz · 08-01-2014, 12:24 PM

Quote:

Originally Posted by ljb643

From the programmer (comments in the code where it does the date check):

(I guess "multi-year-old" means more than 1 year old)

Yep, still I don't think display big warning is the right thing to do

Paulo2 · 08-01-2014, 12:45 PM

It was upgraded in -current, I don't know if there are any side effects if you install
the new version from -current over 14.1

Code:

+--------------------------+
Tue Jun 17 22:19:30 UTC 2014
l/ncurses-5.9-i486-3.txz:  Rebuilt.
  Applied upstream patch ncurses-5.9-20140308-patch.sh.
  Thanks to comet.berkeley.
n/yptools-2.14-i486-3.txz:  Rebuilt.
  Corrected yppasswd patch that was causing password changes to fail.
  Thanks to Henrik Carlqvist.
xap/xscreensaver-5.29-i486-1.txz:  Upgraded.
+--------------------------+

Code:

+--------------------------+
Tue Jun 17 22:19:30 UTC 2014
l/ncurses-5.9-x86_64-3.txz:  Rebuilt.
  Applied upstream patch ncurses-5.9-20140308-patch.sh.
  Thanks to comet.berkeley.
n/yptools-2.14-x86_64-3.txz:  Rebuilt.
  Corrected yppasswd patch that was causing password changes to fail.
  Thanks to Henrik Carlqvist.
xap/xscreensaver-5.29-x86_64-1.txz:  Upgraded.
+--------------------------+

volkerdi · 08-01-2014, 02:34 PM

Quote:

Originally Posted by keefaz

Yep, still I don't think display big warning is the right thing to do

I think patching out the big warning seems like the best course of action. Hardcoding a software expiration date is seldom helpful.

The GNUinator · 08-01-2014, 11:28 PM

SOLVED:

turns out a new version is in today's Slackpkg update. No more error message. Thank you to all who posted in this thread.

The GNUinator

keefaz · 08-02-2014, 08:40 AM

Quote:

Originally Posted by volkerdi

I think patching out the big warning seems like the best course of action. Hardcoding a software expiration date is seldom helpful.

Here is a patch (tested) that basically removes the expiration time test function [ senescent_p() ] and all references to it

[edit]
I just see you your patch, bah I did it another way

MasterOfMagic · 08-11-2014, 12:43 PM

When running with this new version I get the following error when I lock the screen:
"xscreensaver: 12:42:42: couldn't grab pointer (AlreadyGrabbed)"

Edit: This only happens when I click on wmclock to lock the display. Running "xscreensaver-command -lock" from an xterm works fine. So I'll look at wmclock for this. Thanks for all of your help.