/usr/libexec/gnome-remote-desktop-daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3

To provide some context, when this crash can happen: It can happen, after attempting to start a remote desktop session, when the screen is locked.
In such case, g-s directly refuses the start request and therefore the lifetime of the rdpgfx thread in FreeRDP is very short.

The journal message for this looks like this:
`Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited`

Now, the error here is, that FreeRDP does not correctly wait for the rdpgfx thread to be created and this can lead to in this situation, that the rdpgfx thread is not teared down, when stopping the session, which can can lead to segfaults, like in this report or to memory corruption.

Personally, I was not able to reproduce the error. However, with the help of the journal entries I was able to find this cause.
https://github.com/FreeRDP/FreeRDP/pull/7836 takes care of the problem.

Sessions, that are not locked, should not be affected by this issue.

This needed rebasing onto to the security update 2.6.1+dfsg1-3ubuntu2.1. To save time I've done that and sponsored a re-upload for you, using the version string 2.6.1+dfsg1-3ubuntu2.2. I trust that's OK.

This upload contains a significant rewrite of thread handling code. Normally that would be unsuitable for an SRU on the basis of a microrelease update. It's not something I'd expect to see in an upstream "stable" branch, and I think casts doubt on whether this is an appropriate upstream project to take "stable" microrelease updates from in general without a change-by-change analysis an individual justifications each time.

So, thank you for submitting this change on an individual basis. I think the error counts for this particular issue do justify the SRU in this case.

However, I do think there is considerable regression risk. Because of the nature of the change being introduced, the scope of a regression appears to be wide. Deadlocks, crashes and other race conditions may appear anywhere. Please look out for this during SRU verification.

Hello errors.ubuntu.com, or anyone else affected,

Accepted freerdp2 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/freerdp2/2.6.1+dfsg1-3ubuntu2.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

I successfully completed Test Case 2. Test Case 1 is not really testable until we release this to jammy-updates. We will be watching errors.ubuntu.com to see if this error reappears there.

There are a surprising number of people with -proposed enabled in stable releases of Ubuntu so the Ubuntu Error Tracker would actually be a valuable source of information right now. We'd want to look for individual crashes from systems with the binary version of freerdp2 packages from -proposed installed. I have some code to do this, which may require some minor updates, and will try and run this query before the end of 2022-06-30. If I don't get to it let's go ahead and release since it is a large source of crashes.

I constructed a database query which searched for crashes in the bucket linked to from the bug description and checked the Dependencies field in the those crashes for the version of libfreerdp2-2 installed. I'll attach the full results of the query but the summary follows:

    121 2.6.1+dfsg1-3ubuntu1
     41 2.6.1+dfsg1-3ubuntu2
     73 2.6.1+dfsg1-3ubuntu2.1

Subsequently, I'm going to accept the new version to -proposed.

This bug was fixed in the package freerdp2 - 2.6.1+dfsg1-3ubuntu2.2

---------------
freerdp2 (2.6.1+dfsg1-3ubuntu2.2) jammy; urgency=medium

  * Cherry-pick !7836 to fix a crash seen when trying to connect to
    an Ubuntu/GNOME session when the screen is locked LP: #1970994

 -- Jeremy Bicha <email address hidden> Wed, 01 Jun 2022 13:51:01 -0400

The verification of the Stable Release Update for freerdp2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.