Re: How to ensure that rygel starts after tracker?

[Mehmet Giritli <mgiritli giritli eu>]

On Fri, 2012-10-19 at 15:08 +0300, Mehmet Giritli wrote:
> On Fri, 2012-10-19 at 12:39 +0200, Jens Georg wrote:
> > On Fr, 2012-10-19 at 13:24 +0300, Mehmet Giritli wrote:
> > > On Fri, 2012-10-19 at 12:16 +0200, Jens Georg wrote:
> > > > On Fr, 2012-10-19 at 13:05 +0300, Mehmet Giritli wrote:
> > > > 
> > > > > > That was only my theory. Perhaps something else is going on.
> > > > > > 
> > > > > > tracker: 0.14.2
> > > > > > rygel: 0.14.3
> > > > > > 
> > > > > 
> > > > > Any more comments about this one Jens? 
> > > > 
> > > > Sorry, your reply drowned in my inbox.
> > > > 
> > > > > 
> > > > > The problem is that I do not know a way to see whats going on while
> > > > > rygel starts up. How can I do that? Surely there must be a way. 
> > > > 
> > > > Yes. Start rygel with 
> > > > 
> > > > G_MESSAGES_DEBUG=all rygel -g 5.
> > > > 
> > > 
> > > The problem occurs only at the first time rygel is run after a fresh
> > > boot and the first succeeding gnome login. Therefore, I need a way to
> > > record debug log through gnome-session. How can I do that? My rygel
> > > entry in gnome-session-properties is like this:
> > > 
> > > dbus-send --type=method_call
> > > --dest=org.freedesktop.DBus /org/freedesktop/DBus
> > > org.freedesktop.DBus.StartServiceByName string:org.gnome.Rygel1 uint32:0
> > > 
> > > 
> > > Starting from a terminal does not show the actual problem...
> > 
> > You need to create a wrapper script then:
> > 
> > #!/bin/sh
> > 
> > export G_MESSAGES_DEBUG=all
> > /usr/bin/rygel -g 5 >/tmp/rygel-startup.log 2>&1
> > 
> > and modify the "Exec" line
> > in /usr/share/dbus-1/services/org.gnome.Rygel1.service to use that
> > script. The log will be in /tmp/rygel-startup.log then.
> > 
> 
> I am attaching the log file I obtained. I hope it helps. Currently (at
> the time of this log file generated) Rhythmbox can not see the tracker
> library, but only itself.

Hey Jens,

Did the log file I sent tell you anything about my problem at all? I am
still having the same problem at startup...