New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client/X11: Trying to paste copied files from a server crashes xfreerdp #10072
Comments
@pnowack ok, this is really a puzzle... |
I did my test here with g-r-d-46 on the server side and with xfreerdp(3) on the client side in a GNOME 46 environment (both systems are Archlinux). I guess though a Ubuntu 24.04 LTS Beta or Fedora 40 Beta (with disabled SELinux) should work too as reproduction systems. |
@pnowack I´m currently preparing another batch of |
Not sure whether this can be tracked, but normally the only way, the Another idea could be an issue when we cast things, I think I saw something in the commit history that there were some changes regarding that. |
@pnowack can you do a bisect? |
Will try this week. It did work before christmas, when we had the 3.0 release there. |
hmm, did not really see any relevant changes since then :/ |
Ok, it looks like the source for this crash is external. I built now FreeRDP-3.0.0 (at that 3.0.0 tag) and I can reproduce the crash there as well. |
closing this. |
Affected version master, also affects current 3.4.0 release.
Reproduction steps:
Upon switching to nautilus, xfreerdp fetches the file list and there immediately crashes with the following backtrace:
It seems that something set the
children
list of theroot_dir
toNULL
, which should not happen. I don't know what triggers that part, but this leads to xfreerdp crashing when trying to create a new FUSE directory (for the clip data id) under the FUSE root dir, since there thechildren
list ofroot_dir
is somehowNULL
.I've looked through the commit history of
xf_cliprdr.c
andclient_cliprdr_file.c
and couldn't find a fishy change since when I reworked the clipboard part. It did work, when I reworked that part, so not sure what introduced this regression here.I could though reproduce this issue on multiple different machines without a single case, where the crash with the reproduction steps above, did not happen. Maybe we have some memory corruption here, though one, that always triggers.
The text was updated successfully, but these errors were encountered: