From: 12345@whatismyemailaddress.xyz   
      
   On Mon, 12 Dec 2022 19:15:28 +0000, Chris Elvidge wrote:   
      
   > On 12/12/2022 15:15, John Smith wrote:   
   >> 	This is happening under Virtual Box in Slackware 15.0. Since the   
   >> VM is Debian 11, this may be more a Debian kind of thing, but Slackware   
   >> people seem to be more savvy when it comes to such technical details.   
   >>   
   >> 	I have this Debian 11 VM running Xfce. I killed the screensaver   
   >> and power manager daemon in this Xfce session, for I have no need for   
   >> them. When I left this sit for a while (maybe half an hour or so) on   
   >> trying to do so the keyboard is completely unresponsive in this VM.   
   >> Only the keyboard - the mouse is still working fine.   
   >>   
   >> 	The thing is, when I elicit a software keyboard from Virtual Box,   
   >> by doing Input -> Keyboard -> Soft Keyboard at the Virtual Box menu in   
   >> the window where the VM is running, I can type characters all right in   
   >> the VM - for example, into a terminal emulator already running in that   
   >> VM - and from that point onward I can use my real keyboard in that VM   
   >> without any problems - until such time that I stop using it for half an   
   >> hour or so again.   
   >>   
   >> 	This seems to point in the direction of some issue with Virtual   
   >> Box itself. Any ideas?   
   >>   
   >>   
   > AIUI, it's a problem with the (x and) xfce screensaver(s) in the virtual   
   > machine. Remove them both (from Debian), don't just disable them.   
      
   	Thanks. The thing is, no screensaver is running in the Debian VM.   
   How would the presence of those components cause such problem if they are   
   not running?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)