similar to: samba 4 PAM and xscreensaver

On 9 April 2018 at 04:47, Tom Grace <lists-in at deathbycomputers.co.uk> wrote: > On 09/04/2018 07:47, Nicolas Kovacs wrote: >> I didn't know a screensaver was that critical. > > It's critical in that XScreenSaver deals with locking the screen/dealing > with passwords. I believe the fancy animation bits are separate. >

Le 09/04/2018 ? 00:33, Keith Keller a ?crit?: > I think you can use the --no-splash switch. > > https://www.jwz.org/xscreensaver/man1.html > > There's probably also a config setting in .xscreensaver. No, there's no configuration setting. And no way to turn it off. Patrick Volkerding wrote about this some time ago in Slackware's ChangeLog.txt, explaining he decided to

Hi, I'm currently moving all our local school's desktop clients from Slackware 14.1 to CentOS 7 + Xfce. Right now I'm fine-tuning the default user profile. I have a problem with XScreenSaver. The application per se works very well. Only there's a hard-coded pop-up window that reminds the user that he's not running the latest version. So, if I'm running version 5.36 as

http://bugs.freedesktop.org/show_bug.cgi?id=19854 Summary: xscreensaver fails to run (regression) Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Le 09/04/2018 ? 03:04, Chris Adams a ?crit?: > It's Open Source - patching to remove such a nag is legal and a service > to the users. > > It's a screensaver program - how many updates does it need anyway? If > it is just updates to add more fancy animations, there is zero reason to > demand people upgrade. Here's the exact response I got from the developer after

Hi, since some weeks i have a strange bug / problem at our gentoo linux clients sometimes the user is unable to unlock the xscreensaver via pam / winbindd if i restart the winbindd, the unlock works. winbindd log https://pastebin.com/qVzenH47 it makes no diffrence witch of our ad/dcs respond to the client. net ads info LDAP server name: 1 or 2 or 3 (our rodc) around 40 days ago

The people at Debian were chuntering that it'd be a good idea for xscreensaver to ask ssh-add to drop its keys when it blanked the screen. Would the attached script (which does just that) be worth adding to the contrib directory? It would also be useful to give ssh-agent a facility to drop its keys after some time of inactivity. How easy would this be to implement? Thanks, Andrew

On Sun, Apr 8, 2018 at 1:06 PM Nicolas Kovacs <info at microlinux.fr> wrote: > Le 08/04/2018 ? 13:54, Nicolas Kovacs a ?crit : > > As far as I can tell, there would be several solutions to this problem. > > > > 1. Ask the EPEL maintainers to keep the application up-to-date. > > > > 2. Patch the darn thing so I don't get the annoying popup. > > >

On Apr 8, 2018, at 07:54, Nicolas Kovacs <info at microlinux.fr> wrote: > > Hi, > > I'm currently moving all our local school's desktop clients from > Slackware 14.1 to CentOS 7 + Xfce. Right now I'm fine-tuning the default > user profile. > > I have a problem with XScreenSaver. The application per se works very > well. Only there's a hard-coded

CentOS Errata and Security Advisory CESA-2007:0322 xscreensaver security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2007-0322.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/xscreensaver-4.10-21.el3.i386.rpm source: updates/SRPMS/xscreensaver-4.10-21.el3.src.rpm You may update your CentOS-3 i386 installations

CentOS Errata and Security Advisory CESA-2007:0322 xscreensaver security update for CentOS 3 x86_64: https://rhn.redhat.com/errata/RHSA-2007-0322.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/xscreensaver-4.10-21.el3.x86_64.rpm source: updates/SRPMS/xscreensaver-4.10-21.el3.src.rpm You may update your CentOS-3 x86_64

CentOS Errata and Security Advisory CESA-2006:0498 xscreensaver security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2006-0498.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/xscreensaver-4.10-20.i386.rpm source: updates/SRPMS/xscreensaver-4.10-20.src.rpm You may update your CentOS-3 i386 installations by

CentOS Errata and Security Advisory CESA-2006:0498 xscreensaver security update for CentOS 3 x86_64: https://rhn.redhat.com/errata/RHSA-2006-0498.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/xscreensaver-4.10-20.x86_64.rpm source: updates/SRPMS/xscreensaver-4.10-20.src.rpm You may update your CentOS-3 x86_64

A new xscreensaver package is available for CentOS-3 x86_64. Refer to https://rhn.redhat.com/errata/RHBA-2004-443.html. RPMS/xscreensaver-4.10-8.x86_64.rpm SRPMS/xscreensaver-4.10-8.src.rpm Execute "yum update xscreensaver" to apply. Will Dinkel Chief Technology Officer Team HPC, Inc. 785-542-2135 x304 wdinkel at teamhpc.com http://www.teamhpc.com -------------- next part

For an out-of-box Centos install that utilizes PAM for xscreensaver within both gnome and kde, what factors would lead to xscreensaver not being able to properly unlock the user? I reviewed the logs and nothing helped. I performed ldd on xscreensaver and an ls -l on each dependency proved they were all there. The system uses local /etc/passwd and /etc/shadow files for authentication - no

On Sun, April 8, 2018 6:54 am, Nicolas Kovacs wrote: > Hi, > > I'm currently moving all our local school's desktop clients from > Slackware 14.1 to CentOS 7 + Xfce. Right now I'm fine-tuning the default > user profile. This is a big change, so it must be prompted by substantial reason. Would you mind share it: what about slackware was that bad to prompt it. Thanks a

On 2018-04-08, Nicolas Kovacs <info at microlinux.fr> wrote: > > As far as I can tell, there would be several solutions to this problem. > > 1. Ask the EPEL maintainers to keep the application up-to-date. > > 2. Patch the darn thing so I don't get the annoying popup. > > 3. Maintain my own up-to-date version of XScreenSaver in my private repo. I think you can use

CentOS Errata and Security Advisory 2007:0322 https://rhn.redhat.com/errata/RHSA-2007-0322.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/xscreensaver-4.10-21.el3.s390.rpm s390x: updates/s390x/RPMS/xscreensaver-4.10-21.el3.s390x.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2007:0322-01 Important: xscreensaver security update Files available: xscreensaver-3.33-4.rhel21.5.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum

CentOS Errata and Security Advisory 2007:0322 https://rhn.redhat.com/errata/RHSA-2007-0322.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/xscreensaver-4.18-5.rhel4.14.s390.rpm s390x: updates/s390x/RPMS/xscreensaver-4.18-5.rhel4.14.s390x.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently