akallabeth

@Nabla128k that sounds good (that it is faster) and strengthens the assumption that it is driver dependent (it uses qt instead of x11 for drawing, which utilize different optimizations/drawing primitives)....

Not seen such behaviour so far. You're using our nightly builds I assume? Which desktop environment dou you use, it is most likely related to that. (Key bindings, special keys?)

@skummer101 please add a bit more of information. * Command line used * Did you try with our nightly builds (or some current version) * which remote os?

@skummer101 ok, then it would be interesting if adding `/gfx:avc444 /network:auto` changes something (switches to newer rails mode). Other than that there is only debugging the whole session and finding...

I´ve reworked some parts of the input handling with https://github.com/FreeRDP/FreeRDP/pull/6323 Any change with that?

@pavel-zhigulin you´re talking about `wlfreerdp`, this issue is for `xfreerdp` (different clients)

I´ve thought about this a bit, could anyone experiencing this issue try to minimize all `xfreerdp` windows with the appropriate keyboard shortcut? (e.g. click on some other application window first...

@Nixname5 ok, that is interesting. So, there is an overlay window once `xfreerdp` is running you´re clicking on?

@Fantu as discussed in the matrix channel, this is most likely the case. * The optimizations were developed for 32 bit arm machines and are not optimized for the wider...

Hi, as for command line option, you only have `VID:PID` on linux (bus ID are changing when you attach on a different port). Best would be to have bothe, blacklist...