-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jul 03, 2017 at 07:35:09AM -0700, tony mollica wrote:
> I really don't know what's happening regarding this issue [...]
> the printer was stopped with no other indications of what was
> happening [...] AND it keeps the extruder
> and platen hea
Not worth the bother, I agree.
I just removed all the autostart stuff and that seems to work.
Tony
On 07/03/2017 08:43 AM, Curt wrote:
On 2017-07-03, tony mollica wrote:
Thanks for the link. Very interesting.
The link mentions a light-locker-settings package or configuration. It
would nic
On 2017-07-03, tony mollica wrote:
> Thanks for the link. Very interesting.
> The link mentions a light-locker-settings package or configuration. It
> would nice to know if that package/application actually produces the
> light-locker.conf file.
Yeah, apparently there's a config utility call
Thanks for the link. Very interesting.
The link mentions a light-locker-settings package or configuration. It
would nice to know if that package/application actually produces the
light-locker.conf file.
Tony
On 07/03/2017 07:31 AM, Curt wrote:
On 2017-07-03, tony mollica wrote:
My progra
I really don't know what's happening regarding this issue. I just
relayed what I saw occurring. It appears the processes are still
'running' but suspended. The information going from the computer to the
printer was stopped with no other indications of what was happening. In
my circumstance
On 2017-07-03, tony mollica wrote:
> My programs were also still in place but they stopped processing until I
> logged back in via the light-locker screen. After that, the processing
> re-started (evidenced by the printer continuing merrily on it's way) and
> then I continued to log into the f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jul 02, 2017 at 08:19:51PM -0700, tony mollica wrote:
> My programs were also still in place but they stopped processing
> until I logged back in via the light-locker screen.
This approach seems to be so heavy handed that I'm not sure I'd
want
My programs were also still in place but they stopped processing until I
logged back in via the light-locker screen. After that, the processing
re-started (evidenced by the printer continuing merrily on it's way) and
then I continued to log into the full desktop through the
mate-screensaver lo
wrote:
> On Sat, Jul 01, 2017 at 10:20:13AM -0700, Mike Kupfer wrote:
> > This doesn't sound to me like you're being logged out. Rather it sounds
> > like light-locker is locking your screen, which is does by bringing up a
> > new lightdm instance.
>
> But what happens then to the current X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jul 01, 2017 at 10:20:13AM -0700, Mike Kupfer wrote:
> tony mollica wrote:
>
> > I let the xscreensaver run overnight and it appears that after some
> > time, whatever amount of time that is, the system still falls back to
> > the lightdm gree
tony mollica wrote:
> I let the xscreensaver run overnight and it appears that after some
> time, whatever amount of time that is, the system still falls back to
> the lightdm greeter for logging in. However, after logging in again I
> now get the xscreensaver unlock input window,
This doesn't s
FOUND IT! I think.
And there's a lot of discussion about it, too.
The issue is that Stretch has implemented light-locker as a screen
locker for security purposes. A search for 'debian light-locker'
brings up a lot of discussion and bug reports concerning this new
standard addition to Stretc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jul 01, 2017 at 08:13:26AM -0700, tony mollica wrote:
> Yet more information on this particular issue.
>
> I let the xscreensaver run overnight and it appears that after some
> time, whatever amount of time that is, the system still falls back
Yet more information on this particular issue.
I let the xscreensaver run overnight and it appears that after some
time, whatever amount of time that is, the system still falls back to
the lightdm greeter for logging in. However, after logging in again I
now get the xscreensaver unlock input
Concerning this issue, I removed the mate-screensaver and installed
xscreensaver and while it certainly doesn't have as polished an
appearance as the mate version, it works.
It does the same thing, locks the screen and does not drop back to the
lightdm greeter logon and doesn't suspend in-progre
This bug report sounds familiar but I find no evidence of anything that
appears to be related to this in any of the logs.
The only screensaver loaded is the mate-screensaver. If I disable the
screensaver via the idle time and lock options and then lock the screen
manually, it stays at the mat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 29, 2017 at 08:43:26AM -0700, tony mollica wrote:
> Hello, yet again, and dropping the html.
>
> Here's the problem. I use this computer, previously v8, now v9, for
> 3D printing. The old system worked perfectly in that the
> screensaver
Hello, yet again, and dropping the html.
Here's the problem. I use this computer, previously v8, now v9, for 3D
printing. The old system worked perfectly in that the screensaver did
it's job BUT kept me logged in forever. The new system doesn't do this.
The screensaver set off and after so
18 matches
Mail list logo
