Author Topic: Slickedit "lost" keyboard input  (Read 336 times)

astromme

  • Senior Community Member
  • Posts: 150
  • Hero Points: 1
Slickedit "lost" keyboard input
« on: September 26, 2023, 09:22:32 PM »
SlickEdit Pro 2023 (v28.0.0.3 64-bit Qt5) on Ubuntu 22.04.2 LTS with multiple monitors.

Whilst I was editing away, suddenly keyboard input did nothing in Slickedit.  I could click on File->Save to save my work.  I opened Key Bindings and tried to enter something there, no go, nor in the Options search.

When this started, I saw "Background tagging is searching for files to tag in tag file '<one of my apps>.vtg'.

I could click to other windows and the keyboard worked fine.

I File->Exit-ed Slickedit and restarted it and the keyboard started to work again.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1818
  • Hero Points: 151
Re: Slickedit "lost" keyboard input
« Reply #1 on: September 27, 2023, 01:34:04 PM »
Hmm, I don't think we've hit this before.  Is there anything in your .slickedit/28.0.0/logs/vs.log file?  If you know the time frame it happened, run "journalctl -xe" and scan back to that time period and see if you see any references to vs_exe, or anything that might be wayland/xorg related.

Are you using the default GNOME environment for Ubuntu 22?  Is it the default Wayland session, or are you using the GNOME on Xorg session?

astromme

  • Senior Community Member
  • Posts: 150
  • Hero Points: 1
Re: Slickedit "lost" keyboard input
« Reply #2 on: September 27, 2023, 05:36:01 PM »
Per https://askubuntu.com/questions/904940/how-can-i-tell-if-i-am-running-wayland

Code: [Select]
stromme@WORK:~/.slickedit/28.0.0/logs$ echo $XDG_SESSION_TYPE
x11

So it looks like no wayland.

I don't see anything in journalctl either:
Code: [Select]
stromme@WORK:~/.slickedit/28.0.0/logs$ journalctl -xe --since "2023-09-25" | grep x11
stromme@WORK:~/.slickedit/28.0.0/logs$ journalctl -xe --since "2023-09-25" | grep xorg
stromme@WORK:~/.slickedit/28.0.0/logs$ journalctl -xe --since "2023-09-25" | grep vs
stromme@WORK:~/.slickedit/28.0.0/logs$ journalctl -xe --since "2023-09-25" | grep wayland
stromme@WORK:~/.slickedit/28.0.0/logs$

Without the grep there's plenty there.

Also, nothing in vs.log - the last entry was over a week before this problem.

Anything I should do if it happens again?

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1818
  • Hero Points: 151
Re: Slickedit "lost" keyboard input
« Reply #3 on: September 27, 2023, 05:57:00 PM »
I've attached a bash script that you can run to collect information on the active x11 windows.  It was written for another problem, but it should let me at least see if there's something unexpected in the window hierarchy that could interfere with keyboard focus.  The script saves its output to /tmp/xwi_capture.txt.  If you get that while it is stuck, you can post that file or PM me with the contents.

I'm reviewing some focus related commits, I'll update the thread if I find anything that looks wrong.

astromme

  • Senior Community Member
  • Posts: 150
  • Hero Points: 1
Re: Slickedit "lost" keyboard input
« Reply #4 on: September 27, 2023, 11:55:21 PM »
I tried PMing you twice, and it said "Your message has been sent successfully." but when I look in My Messages->Sent Items, nothing is there..

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1818
  • Hero Points: 151
Re: Slickedit "lost" keyboard input
« Reply #5 on: September 29, 2023, 12:42:51 PM »
I got your last PM.  re: firefox - I've not heard of an input delay like that happening except extreme cases with a lot of swapping going on.  (and I don't think it's swapping in your case, since everything would be bogged down, it would be hard to miss).

I didn't see anything out of order in the capture so far.  Still have a couple things to check. 

I do have something you can try that will rule out one way the keyboard input can be redirected.  When you start SlickEdit, start it from the command line like this, and see if you still run into the problem:
Code: [Select]
XMODIFIERS="@im=scim" PATH_TO_INSTALL/bin/vs +new

astromme

  • Senior Community Member
  • Posts: 150
  • Hero Points: 1
Re: Slickedit "lost" keyboard input
« Reply #6 on: September 29, 2023, 07:02:44 PM »
Yeah, normally my fan spins up and sounds like a jet engine when things bog down.. then I check top and free.

I fired it up with your command line and the keyboard is fine.

I haven't seen this happen again, so maybe it was just a one off.. if I see it more, I'll regularly run it the way you said.