You are not logged in.
Pages: 1
After at least running pacman in an xterm window, typing is no longer accepted.
I have to click outside the window, then back inside to get an active cursor, and more typing can occur.
I am running xfce4-session/xfwm4 under lxdm.
Is there something I can do to make typing work without clicking out/in? This started after upgrading to Linux 5.
uname -a gives ...
5.5.6-arch1-1 #1 SMP PREEMPT Mon, 24 Feb 2020 12:20:16 +0000 x86_64 GNU/Linux Last edited by OrigBitmancer (2020-03-10 23:30:38)
Offline
What does "running pacman" mean exactly?
Just "pacman" will yell an error and return, is it maybe a -Syu, taking quite a while to complete?
Is it time-without-input driven?
Offline
“Running pacman” === after successfully executing pacman -Syuv
Time-without-input ? You mean, have I done other window operations and returned?
Offline
“Running pacman” === after successfully executing pacman -Syuv
Time-without-input ? You mean, have I done other window operations and returned?
Can you explain exactly what you are doing and seeing in detail?
Your problem is strange because pacman is just a console program. It only knows how to print text in the terminal. It doesn't have the power to do anything to your window environment.
From what you described earlier, there must be something else happening. I'm thinking losing focus for the window means some other window has opened. If there's nothing visible on the desktop, maybe it's a window that closed immediately.
Offline
I meant whether you start a console program (or not) and leave the system untouched for a some minutes (no interaction and esp. no keyboard interaction at all)
There could be some power saving feature (usb or bluetooth) that removes the keyboard and causes the input to go nowhere.
As Ropid mentioned, there's about a zero chance that pacman shuffles the input focus of the display server. Coincidence isn't correlation.
Offline
Do all pacman commands have this effect? Does a full update immediately after a full update have the same effect (the second update should complete almost immediately).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
After dozens of repeatable events with this pathology, I am now having trouble generating the error.
I beg your collective patience.
Edit: I now have more evidence.
The last command entered in the window was more(1), then later a screenblanker ran a plain blank screen.
The window was in Workspace 2 by itself.
I think @seth is on the right track. I might have colliding screensavers. I will investigate.
Edit 2: @seth was indeed on the right track. At some time in the distant past, I had both Cinnamon and X screensavers invoked.
Fixed.
Thanks to everybody.
Last edited by OrigBitmancer (2020-03-10 23:30:04)
Offline
Pages: 1