akallabeth

Don´t have access to the redhat bug tracker sorry :/ As for the trace, this trace is odd. `lodepng_info_init` is only used in `rdtk` or `proxy` yet it is in...

@kathenas thank you. Still, the stack trace does not make any sense, there is no such call stack in `2.7.0`, something is very off here. The `lodepng_info_init` should not be...

do you have the same issue when connecting with `xfreerdp` or only with `remmina`?

Ok, found the problem in the stack trace, [core-backtrace](https://bugzilla.redhat.com/attachment.cgi?id=1880789) is proper, but [backtrace](https://bugzilla.redhat.com/attachment.cgi?id=1880788) call stack is wrong.

bug report at remmina https://gitlab.com/Remmina/Remmina/-/issues/2751

@FutureKidBuu 1. does it recover after a few seconds? 2. The screenshot of the log is not very helpful ;)

@FutureKidBuu ok, the log is missing quite a lot of stuff (and your compile did ignore lots of compile warnings about excessive/dangerous logging)

I´d try a `xfreerdp 2>&1 |tee log.txt` to get a consistent log with errors and warnings

@2fly2 which version and client do you use?

@2fly2 `xfreerdp` and `wlfreerdp` will call `handle_window_events` (wayland is just a stub though) the windows client uses the version without callback though, there it might happen that the window is...