Re: [DNG] Screensaver issues

2017-04-05 Thread fsmithred
On 04/05/2017 11:00 AM, goli...@dyne.org wrote: > On 2017-04-05 07:14, fsmithred wrote: >> On 04/04/2017 03:29 PM, goli...@dyne.org wrote: >>> On 2017-04-03 16:50, fsmithred wrote: On 04/02/2017 06:49 PM, goli...@dyne.org wrote: > A few days ago I finally upgraded to the latest stable

Re: [DNG] Screensaver issues

2017-04-05 Thread golinux
On 2017-04-05 07:14, fsmithred wrote: On 04/04/2017 03:29 PM, goli...@dyne.org wrote: On 2017-04-03 16:50, fsmithred wrote: On 04/02/2017 06:49 PM, goli...@dyne.org wrote: A few days ago I finally upgraded to the latest stable kernel 3.16.39-1+deb8u2. Now my screensaver isn't working

Re: [DNG] Screensaver issues

2017-04-05 Thread fsmithred
On 04/04/2017 03:29 PM, goli...@dyne.org wrote: > On 2017-04-03 16:50, fsmithred wrote: >> On 04/02/2017 06:49 PM, goli...@dyne.org wrote: >>> A few days ago I finally upgraded to the latest stable kernel >>> 3.16.39-1+deb8u2. Now my screensaver isn't working properly. :( It >>> keeps losing

Re: [DNG] problem at talk.devuan.org?

2017-04-05 Thread KatolaZ
On Wed, Apr 05, 2017 at 10:37:34AM +0200, Florian Zieboll wrote: [cut] > > It would be great to have the PGP-signed fingerprints of any used > certificate published at "status.devuan.org" or so. > > BTW, status.devuan.org has a certificate issue as well. > Florian, certificates are based on

Re: [DNG] problem at talk.devuan.org?

2017-04-05 Thread Arnt Karlsen
On Wed, 5 Apr 2017 06:35:40 +0200, Miroslav wrote in message <20170405043540.GA9912@g0n.xdwgrp>: > On 170403-23:32+0200, Massimiliano Baldinelli wrote: > > Ciao! > > > > I don't know if its' an already known issue, but since this morning > > I'm getting a SEC_ERROR_EXPIRED_CERTIFICATE when

Re: [DNG] problem at talk.devuan.org?

2017-04-05 Thread Florian Zieboll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 5 Apr 2017 06:35:40 +0200 Miroslav Rovis wrote: > If you usually connect to this site without problems, this error could > mean that someone is trying to impersonate the site, and you shouldn't > continue. >