After upgrading soup, can no longer connect to daap share via libdmapsharing: 'libsoup-CRITICAL **: soup_uri_new_with_base: assertion `base == NULL || SOUP_URI_IS_VALID (base)' failed'

Bug #929133 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libsoup2.4 (Ubuntu)
New
Undecided
Unassigned
Precise
New
Undecided
Unassigned

Bug Description

After upgrading to libsoup2.4-1 (2.37.5-0ubuntu1) I can no longer connect to daap music shares with libdmapsharing applications like rhythmbox. Eg starting rhythmbox in debugging mode

$ rhythmbox -d
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Doing something for state: 0
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Getting DAAP server info
libsoup-CRITICAL **: soup_uri_new_with_base: assertion `base == NULL || SOUP_URI_IS_VALID (base)' failed
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Error building message for http://192.168.2.2:3689//server-info
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Could not get DAAP connection info
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Transitioning to next state from 0
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Doing something for state: 8
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: DAAP done
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: DAAP finish
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Emitting operation done
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Connected callback
(15:20:06) [0x2441460] [rb_daap_source_connection_cb] rb-daap-source.c:606: Connection callback result: failure
(15:20:06) [0x2441460] [release_connection] rb-daap-source.c:582: Releasing connection
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: DAAP connection dispose
(15:20:06) [0x2441460] [libdmapsharing_debug] rb-daap-plugin.c:617: Aborting all pending requests

I thought it might be the '//server-info' in the URL, but I recompiled a test version of libdmapsharing to not have the extra '/' and it still fails:
(15:30:27) [0xc94460] [libdmapsharing_debug] rb-daap-plugin.c:617: Getting DAAP server info
libsoup-CRITICAL **: soup_uri_new_with_base: assertion `base == NULL || SOUP_URI_IS_VALID (base)' failed
(15:30:27) [0xc94460] [libdmapsharing_debug] rb-daap-plugin.c:617: Error building message for http://192.168.2.2:3689/server-info

Downgrading to libsoup2.4 2.36.1-1ubuntu1, it works:
(15:35:39) [0x259d460] [libdmapsharing_debug] rb-daap-plugin.c:617: Getting DAAP server info
(15:35:39) [0x259d460] [libdmapsharing_debug] rb-daap-plugin.c:617: Queued message for http://192.168.2.2:3689//server-info
(15:35:39) [0x259d460] [libdmapsharing_debug] rb-daap-plugin.c:617: Received response from http://192.168.2.2:3689/server-info: 200, OK

summary: After upgrading soup, can no longer connect to daap share via
- libdmapsharing
+ libdmapsharing: 'libsoup-CRITICAL **: soup_uri_new_with_base: assertion
+ `base == NULL || SOUP_URI_IS_VALID (base)' failed'
tags: added: regression-release
Revision history for this message
W. Michael Petullo (mike-flyn) wrote :

This should be fixed by a future version of libsoup. See:

https://bugzilla.gnome.org/show_bug.cgi?id=703694

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.