From: 12345@whatismyemailaddress.xyz   
      
   On Tue, 13 Dec 2022 06:54:53 -0000 (UTC), Henrik Carlqvist wrote:   
      
   > On Mon, 12 Dec 2022 15:15:54 +0000, John Smith wrote:   
   >> 	This seems to point in the direction of some issue with Virtual   
   >> Box itself. Any ideas?   
   >   
   > I know of a user which wasn't using Slackware and VirtualBox but running   
   > Ubuntu and qemu. He got some trouble with the keyboard. It finally   
   > turned out that the trouble went away when he switched from wayland to   
   > Xorg. Could it be that you are running wayland? If so, would it help to   
   > switch to Xorg?   
      
   	It is running X:   
      
   	root         482  0.1  5.1 604852 104100 tty7    Ssl+ Dec11   
   3:34 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -   
   nolisten tcp vt7 -novtswitch   
   	xyz          859  0.0  1.6 240688 32772 ?        Sl   Dec11   
   0:00 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-   
   linux-gnu/xfce4/panel/plugins/libnotification-plugin.so 10 16777226   
   notification-plugin Notification Plugin Notification plugin for the Xfce   
   panel   
      
   	I ended up disabling all screensavers both in the Debian guest   
   and in the Slackware host, and the problem seems to have disappeared.   
   Since the Slackware host is a headless one, which is running a TigerVNC   
   session which I access from a different Slackware system, maybe the issue   
   is a combination of TigerVNC and Debian. Anyway, since a screensaver is   
   superfluous in a TigerVNC session, I'll take this solution.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)