async operations don't correctly use thread default main context
@alexl
Submitted by Alexander Larsson Assigned to gvf..@..e.bugs
Link to original bug (#708743)
Description
All the async operations don't properly do callbacks on the thread default main context.
For instance, g_daemon_file_read_async() calls create_proxy_for_file_async which does a chain of async call, all except possibly the first on the default context, and then at the end calls back to file_read_async_get_proxy_cb which scedules the actual open call without specifying any particular main context.
Instead we should record the default main context in the async operation itself and propagate this through all the async operations that are part of the operation.