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: , , , , , ,

7 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.

Leave a Reply

Your email address will not be published. But if you provide a fake email address, I will likely assume that you are a troll, and not publish your comment.

You may use these HTML tags and attributes: <a href="" title=""> <b> <blockquote cite=""> <code> <em> <i> <s> <strike> <strong> <img src="" width="" height="" style=""> <iframe src="" class=""> <video src="" class="" controls="" loop="" muted="" autoplay="" playsinline=""> <div class=""> <blink> <tt> <u>, or *italics*.