Skip to content
This repository has been archived by the owner on Feb 19, 2025. It is now read-only.

[Bug] After upgrading to v3.8.0 UI is not responding to keyboard inputs. #1754

Closed
2 tasks done
jenish2014 opened this issue Apr 5, 2024 · 5 comments
Closed
2 tasks done
Labels

Comments

@jenish2014
Copy link

Checklist

  • I have used the search function to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.

App version

3.8.0

Windows version

Windows10 - v19045.4170

Steps to reproduce

Install via Chocolatey
Upgrade to v3.8.0

Expected behavior

Dialog box expected to accept keyboard inputs.

Actual behavior

Dialog box is not responding to keyboard inputs. TAB, Shift-TAB or ALT-F4 keys not working.

Logs

No response

@jenish2014 jenish2014 added the bug label Apr 5, 2024
@secured2k
Copy link

I am unable to reproduce this issue (tested via RDP).

@sn0utss
Copy link

sn0utss commented Apr 18, 2024

I'm on Win10 1809 and am experiencing similar. Main UI and network alert notifications are hanging and only occasionally respond to input. Managed to turn off dark theme but issues persisted. Returning to v.3.7.8, works as normal.

If you have any suggestions for troubleshooting I'd be happy to help. Have used this program for many years and v3.8 is the first I've encountered such a thing.

@henrypp
Copy link
Owner

henrypp commented Apr 23, 2024

@sn0utss and TS

it is a duplicate of #1760 (and possible fix)

@henrypp henrypp closed this as completed Apr 23, 2024
@brian6932
Copy link

Not sure how this is a duplicate of my issue though, mine was about a bind being misinterpreted in the wrong context.

@henrypp
Copy link
Owner

henrypp commented Apr 23, 2024

@brian6932 anyway,i cant reproduce this issue,and in ur issue is have fix for this (mb).

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants