Re: [arch-general] fluxbox/xscreensaver xterm unresponsive upon screensaver cancel?
On Tue, Oct 18, 2016 at 12:55:15AM -0500, David C. Rankin wrote: > On 10/11/2016 01:24 AM, Leonid Isaev wrote: > > FWIW, a quick test in a VM doesn't show this behavior. What happens if you > > run > > xscreensaver-command -lock from an xterm? > > I can lock and unlock after several minutes and all is fine. It's when it has > been locked for a day or so with the xterm running that it becomes > unresponsive. > ACPI issue? Not likely because fluxbox doesn't do any acpi-related stuff. It has to be smth else, but I don't know because you describe the problem pretty vaguely... L. -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Re: [arch-general] fluxbox/xscreensaver xterm unresponsive upon screensaver cancel?
On 10/11/2016 01:24 AM, Leonid Isaev wrote: > FWIW, a quick test in a VM doesn't show this behavior. What happens if you run > xscreensaver-command -lock from an xterm? I can lock and unlock after several minutes and all is fine. It's when it has been locked for a day or so with the xterm running that it becomes unresponsive. ACPI issue? -- David C. Rankin, J.D.,P.E.
Re: [arch-general] fluxbox/xscreensaver xterm unresponsive upon screensaver cancel?
On Tue, Oct 11, 2016 at 12:30:15AM -0500, David C. Rankin wrote: > All, > > I'm not sure where to start searching on this problem. I have a server with > fluxbox and xscreensaver enabled. If I'm running xterm when the screensaver > activates, if I return after a couple of hours, the xterm is unresponsive. > (instead of a normal solid black-box cursor, it is a white block cursor with a > thin black outline) At this point, the xterm in non-responsive and I must kill > the window with the [X] window control (top-right) and restart a new session. > > I note that if another application is left running, like firefox, then the > xterm doesn't seem to hang or disconnect (or whatever it is doing). > > I don't know whether to chase this as an xterm issue, an xscreensaver issue > or > a DPMS issue. Has anyone encountered this before? If so, any solutions, or did > you narrow it down to one of (xterm, xscreensaver, DPMS)? Thanks for any > suggestions. FWIW, a quick test in a VM doesn't show this behavior. What happens if you run xscreensaver-command -lock from an xterm? L. -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
