Last chance to give the XScreenSaver 6 beta a try

I think it's looking pretty solid, so I'm probably going to do a non-beta release of it in April, but it would be great to get some more testing feedback before then. Give it a shot, won't you? Details are in my previous post.
Tags: , , , , , ,

11 Responses:

  1. g051051 says:

    Anything particularly interesting shake out of the beta?

    • jwz says:

      There was some irritating compositor nonsense, but mostly it was portability stuff, some cosmetic tweaks, and instructions on how to kneecap KDE.

      And I've learned that autoconf is the devil. Ha, I joke, I joke, I knew that already.

      • Walex says:

        > autoconf is the devil.

        Or perhaps a virus: it spreads by infecting many hosts (other sw projects) and then makes them sick and might even kill the weaker ones. It is the digital flu. :-)

  2. jer says:

    When some(?) of the libraries xscreensaver (-auth?) does or does not link against have been updated, authentication by password always fails. Logs do not show any interesting information from xscreensaver itself.

    Output from two attempts at entering the password (correctly, I am sure!):

    Mar 31 17:14:54 wim unix_chkpwd[10976]: password check failed for user (xxxxxxxx)
    Mar 31 17:14:54 wim xscreensaver-auth: pam_unix(xscreensaver:auth): authentication failure; logname=xxxxxxxx uid=xxxxxxxx euid=xxxxxxxx tty=:0.0 ruser= rhost= user=xxxxxxxx
    Mar 31 17:14:55 wim xscreensaver-auth[10965]: Failed login on display ":0.0" for "xxxxxxxx"
    Mar 31 17:15:03 wim unix_chkpwd[10991]: password check failed for user (xxxxxxxx)
    Mar 31 17:15:03 wim xscreensaver-auth: pam_unix(xscreensaver:auth): authentication failure; logname=xxxxxxxx uid=xxxxxxxx euid=xxxxxxxx tty=:0.0 ruser= rhost= user=xxxxxxxx
    Mar 31 17:15:05 wim xscreensaver-auth[10980]: Failed login on display ":0.0" for "xxxxxxxx"

    • jwz says:

      I think you just said, "I upgraded something and that broke my PAM installation"?

      When PAM reports a login failure, XScreenSaver believes it.

      • jer says:

        No, no updated PAM libraries were involved. It could be X11 libraries or GTK+ libraries or (in the latest instance) Nvidia's proprietary driver's libraries.

        • jwz says:

          PAM says you're not authenticated, you're not authenticated. I don't know what you expect me to do about your upgrade having gone wrong.

  3. Scott says:

    OT but still about xscreensaver, can you answer this old Q?:
    https://askubuntu.com/questions/1100648/use-xscreensaver-at-the-login-screen

    I would like to do it too... could probably hack Lightdm to run xscreensaver before greeter? Or something... but would it be secure? Only you can answer this Q...

    • jwz says:

      There are instructions in the manual that used to work with xdm/gdm. I have no idea whether those instructions still work on so-called "modern" systems, but if you figure it out, let me know!

      • Scott says:

        JWZ FYI: there's not really any way I can figure out because of the gdmflexiserver error(s) xscreensaver prompts when trying to login as a new user... (I'm using the "unstable" 5.45 version from Debian ...there are some work-arounds but not really effective for logging in) xscreensaver is getting a bad rep/rap as your "time-bomb". Congratulations, you've broken Linux... I hope you're happy. :)

        • jwz says:

          Are you under the impression that I wrote gdmflexiserver? Hint: I did not. You have my sympathies that the byzantine house of cards that is the Linux startup sequence is confusing. It certainly is. But, again, it is not my work or my responsibility, and even if I could fix it, I do not have the authority to do so.

          XScreenSaver is working as designed, so in answer to your question, yes, I'm completely happy with it.

          Integration with the moving target of dozens of arbitrarily different Linux and BSD distros, however? That is very much not my problem. Talk to the so-called "maintainers" of the (modified, perpetually out-of-date) forks of XScreenSaver bundled by those distros. If you are having trouble using XScreenSaver on Ubuntu, figure out who built and distributed the XScreenSaver package for Ubuntu. It was, I assure you, not me. I'm sure they know more about Ubuntu than I do, since I know nothing about Ubuntu, having never, ever used it.

          They made their bed, and they can lie in it.