Re: after updating to rygel .22, tracker backend does not work

[Jens Georg <mail jensge org>]

Am 2014-07-29 11:55, schrieb Mehmet Giritli:
> tracker version is 1.0.2 and I see these after the upgrade:
>
> mordor rygel[10766]: (rygel:10766): Rygel-Tracker-CRITICAL **: file
> rygel-tracker-plugin-factory.c: line 220: uncaught error: Error 
> spawning
> command line 'dbus-launch --autolaunch=0bdeae931532301278536d5a00000012
> --binary-syntax --close-stderr': Child process exited with code 1
> (g-spawn-exit-error-quark, 1)

That's the code that is trying to force tracker-store to start. It looks 
like
you don't have a session bus?

> I also see these but don't know if they are related:
>
> Jul 29 12:49:38 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument
> Jul 29 12:49:38 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument
> Jul 29 12:49:38 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument
> Jul 29 12:49:39 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument
> Jul 29 12:49:39 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument
> Jul 29 12:49:40 mordor rygel[10766]: ** (rygel:10766): WARNING **: 
> Error
> sending SSDP packet to 192.168.2.8: Error sending message: Invalid
> argument

That should be a bug in GSSDP, I recommend upgrading to 0.14.9.