Le 08/04/2018 à 14:53, Jonathan Billings a écrit :
> It appears that the spec file actually patches xscreensaver to change
> the time bomb date to be the build time, so you’d only need to
> rebuild it to make it stop. (The EPEL maintainer could too)
>
>
in that XScreenSaver deals with locking the screen/dealing
>> with passwords. I believe the fancy animation bits are separate.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/c
ieve the fancy animation bits are separate.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
xscreensaver is security critical for the following reasons:
1. Several of the screensavers take user
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.
___
CentOS mailing list
> It's not rocket science: someone on your distro's team just needs to
> update it ONCE A YEAR. If that is too onerous for them, then I'd prefer
> that they not distribute my software at all.
And that just goes to show that he knows not what CentOS is - since
clearly he doesn't realise that it
Hello,
On Sun, 08 Apr 2018 18:10:35 -0700 Keith Keller
wrote:
> On 2018-04-08, Nicolas Kovacs wrote:
> > Le 09/04/2018 à 00:33, Keith Keller a écrit :
> >> I think you can use the --no-splash switch.
> >>
> >>
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
On 2018-04-08, Nicolas Kovacs wrote:
> 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
Once upon a time, Nicolas Kovacs said:
> 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 upgrade this single piece of software
> mid-release just to
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
On 2018-04-08, Nicolas Kovacs 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
On Sun, 8 Apr 2018 22:28:04 +0200
Nicolas Kovacs wrote:
> This mister JWZ just blogged and tweeted loudly about it,
He apparently doesn't understand what his own software does, either:
"They had to CLICK OK on a dialog box after they rebooted!!"
The dialog box comes up when you log in, not
;
https://web.archive.org/web/20180408204243/https:/twitter.com/jwz/status/983061118863032320
R. S. Tyler Schroder
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Nicolas Kovacs
Sent: Sunday, April 8, 2018 4:28 PM
To: centos@centos.org
Subject: Re: [CentOS] XScr
Le 08/04/2018 à 21:47, Stephen John Smoogen a écrit :
> Yeah that is pretty classic JWZ... well except he didn’t say something
> anatomically impossible. I think he may have mellowed a bit.
This mister JWZ just blogged and tweeted loudly about it, and it looks
like he hates CentOS as much as he
Le 08/04/2018 à 21:47, Stephen John Smoogen a écrit :
> Yeah that is pretty classic JWZ... well except he didn’t say
> something anatomically impossible. I think he may have mellowed a
> bit. I will see if the EPEL version can be updated. Also to make sure
> that he doesn’t get the bugs since he
On Sun, Apr 8, 2018 at 1:06 PM Nicolas Kovacs 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
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.
>
> 3. Maintain my own up-to-date version
Le 08/04/2018 à 16:25, Valeri Galtsev a écrit :
> 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 lot for your insights!
At the time of the change, about a year ago, I've written a short
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
On Apr 8, 2018, at 07:54, 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.
>
> I have a problem with XScreenSaver. The application
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
Hello to all:
I'd like to thank everyone who offered insight to why xscreensaver lock
wasn't working.
Just this morning I performed a last-minute search, based on some leads,
of possible pam configuration issues. One URL that popped up via google
was
22 matches
Mail list logo