Rhythmbox and grilo-plugins will not display nor play dlna stream

Using the same machine on the same local network, but with a 32-bit and 64-bit build:

32-bit: rhythmbox-3.0.1/grilo-0.2.6/grilo-plugins-0.2.8/totem-pl-parser-3.4.5 plays dlna stream without problems

64-bit: rhythmbox-3.0.1/ grilo-0.2.7/grilo-plugins-0.2.9/totem-pl-parser-3.10.0 shows the dlna server, but not available music files

I don't think this is anything to do with 32-bit/64-bit and in the 64-bit case "grilo-test-ui" shows both the dlna server and the available music files, but rhythmbox only shows the dlna server icon on the left hand side and not the album/artist/all tracks/etc nor the music tracks on the right hand side.

After starting with "rhythmbox -d", waiting until it stops spitting out blah-blah and then enabling grilo in the plugins menu, I get the output below. "[maybe_expand_container] rb-grilo-source.c:1025: not expanding, already browsing" would seem to be relevant.

Does anybody have an idea what the problem might be?


(20:24:11) [0x13e78d0] [rb_shell_player_sync_with_source] rb-shell-player.c:1887: playing source: (nil), active entry: (nil)
(20:24:11) [0x13e78d0] [rb_shell_set_window_title] rb-shell.c:2394: clearing title
(20:24:11) [0x13e78d0] [rb_shell_player_sync_buttons] rb-shell-player.c:1979: syncing with source 0x19cead0
(20:24:11) [0x13e78d0] [rb_statusbar_set_property] rb-statusbar.c:212: selected page 0x19cead0
(20:24:11) [0x13e78d0] [rb_statusbar_sync_status] rb-statusbar.c:291: updating status with: '', '', 999.000000
(20:24:11) [0x13e78d0] [maybe_expand_container] rb-grilo-source.c:1025: not expanding, already browsing
(20:24:12) [0x13e78d0] [sync_window_settings] rb-shell.c:1936: paned position 160
(20:24:12) [0x13e78d0] [sync_window_settings] rb-shell.c:1943: right_paned position 400
(20:24:12) [0x13e78d0] [sync_window_settings] rb-shell.c:1950: si

And also:

(rhythmbox:13168): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid).  Unable to remove object from construction_objects list, so memory was probably just leaked.  Please use GInitable instead.