After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653707 - Problem in using non-default GMainContext with SoupSessionAsync
Problem in using non-default GMainContext with SoupSessionAsync
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: API
2.34.x
Other Linux
: Normal major
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2011-06-30 04:00 UTC by Aneesh Bhasin
Modified: 2011-07-31 15:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test case to show the bug in soup_request_send_async with non-default GMainContext (1.93 KB, text/plain)
2011-06-30 04:00 UTC, Aneesh Bhasin 		Details

Description Aneesh Bhasin 2011-06-30 04:00:54 UTC 
Created attachment 190986 [details]
Test case to show the bug in soup_request_send_async with non-default GMainContext

The soup_request_send_async API does not work properly with non-default GMainContext. 
The callback registered with soup_request_send_async is not called when the async-context property is set to a non-default context.
The attached test case shows this issue : in case of default GMainContext both gotHeadersCallback and sendRequestCallback are called. But in case of non-default GMainContext only gotHeadersCallback is called.
Comment 1 Dan Winship 2011-07-31 15:33:52 UTC 
fixed in git master. thanks for the bug report