I've applied v0.9.15 milestone to some but not finished.
matt335672
@matt335672
Agreed about the logging. 1742 could potentially be left out. It's quite a big change and I've not looked at it yet. It's also dependent on 1738.
aquesnel
@aquesnel
@metalefty for v0.9.15 I'd recommend including #1753 since it fixes some logging changes that was introduced since v0.9.14. I agree with @matt335672 that #1742 can be left out of v0.9.15 since there are still more logging related pull requests that I plan on submitting in the future.
@metalefty when you have a chance can you please take a look at #1738 and let me know if there is additional feedback that needs to be completed before merging?
metalefty
@metalefty
hi, i'll look them one by one
metalefty
@metalefty
I remember @matt335672 implemented the feature to turn off FUSE by config. Is my memory right?
I believe the xrdp NEWS page is now up-to-date as far as my recent merge of neutrinolabs/xrdp#1703 (commit aa5c5daf7e1867fd349f410b6a0d4dd5d2d102c4).
metalefty
@metalefty
thanks alot!
metalefty
@metalefty
Regarding known issues, I confirmed #965 doesn't reproduce with current Windows 10. So I'm removing it from NEWS.
metalefty
@metalefty
After merging #1753, I'll perform a test for 1 or 2 days. Then I'll start to release v0.9.15.
matt335672
@matt335672
@metalefty - are you happy to give me write access to NeutrinoRDP? I've raised a pretty trivial PR there but I'm unable to merge it. Thanks.
Issa
@gamersalpha
yooooo
XRDp works good, but What got not sound
_
that's razy
NO sound, why
metalefty
@metalefty
I remember I don’t have enough privilege to do that but I’ll give it a try
metalefty
@metalefty
@matt335672 unfortunately, I don't have any write access to NeutrinoRDP. Jay is responsible for that.
matt335672
@matt335672
Thanks for trying!
@jsorg71 - Are you happy to give me write access to the NeutrinoRDP repository? Thanks.
metalefty
@metalefty
I've merged all PRs to be merged before v0.9.15. Please don't anything until the release announcement.
the rest thing we need to finish is the document, especially NEWS.
metalefty
@metalefty
I'm checking the known issues part. #965 is no longer an issue. We did nothing with #1266 and it should be addressed to be protocol compliant.
However, FreeRDP 2.2.0 can connect to xrdp even without +glyph-cache. I guess something has been changed on the FreeRDP side.
So we can remove #1266 entry from the known issues part but keep it open.
metalefty
@metalefty
@matt335672@aquesnel BTW, I wrote down some ideas on logging on #1762. Any feedback is welcome.
Pininamix
@Pininamix
Hello, I have this issue trying to RDP in to a Suse server from Debian server, I get this: VNC connecting to 127.0.0.1:5923, VNC error, Problem connecting, some problem.
Seslog shows:
[20201226-10:57:27] [ERROR] X server for display 23 startup timeout [20201226-10:57:27] [ERROR] another Xserver might already be active on display 23 - see log
Help please I have not been able to find a solution for this in internet this was working before Suse did an upgrade.
OS: SUSE Linux 12 SP5 x86_64
metalefty
@metalefty
@Pininamix Did you read the welcome message shown before joining this room?
Pininamix
@Pininamix
Not really.
!welcome
My apologies if this is the wrong place to look for help.
metalefty
@metalefty
no problem but the welcome message explains the room named xrdp-questions is the appropriate place.