Hi Jens, thanks for your help; funny thing happened when I wanted to do a tcpdump on Onkio to send to you.
As I always do, I first tested that I have a working setup using XBMC, and got this: (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:151: HTTP HEAD request for URI 'http://192.168.1.113:1122/GstLaunch/i/YnVtcGFuZGdyaW5k.mp3'. Headers: (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: User-Agent : XBMC/12.1 Git:Unknown (Linux; Fedora release 16 (Verne); 3.6.11-4.fc16.i686.PAE i686; http://www.xbmc.org) (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Host : 192.168.1.113:1122 (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Accept : */* (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Connection : keep-alive (rygel:5718): Rygel-DEBUG: rygel-http-get.vala:182: Following HTTP headers appended to response: (rygel:5718): Rygel-DEBUG: rygel-http-get.vala:184: Date : Wed, 03 Apr 2013 03:29:28 GMT (rygel:5718): Rygel-DEBUG: rygel-http-get.vala:184: Content-Type : audio/mpeg (rygel:5718): Rygel-DEBUG: rygel-http-get.vala:184: contentFeatures.dlna.org: * (rygel:5718): Rygel-DEBUG: rygel-http-get.vala:184: Connection : close (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:151: HTTP GET request for URI 'http://192.168.1.113:1122/GstLaunch/i/YnVtcGFuZGdyaW5k.mp3'. Headers: (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Range : bytes=0- (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: User-Agent : XBMC/12.1 Git:Unknown (Linux; Fedora release 16 (Verne); 3.6.11-4.fc16.i686.PAE i686; http://www.xbmc.org) (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Host : 192.168.1.113:1122 (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Accept : */* (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:155: Connection : keep-alive (rygel:5718): Rygel-WARNING **: rygel-http-request.vala:100: Invalid seek request (rygel:5718): Rygel-DEBUG: rygel-http-server.vala:136: HTTP GET request for URI 'http://192.168.1.113:1122/GstLaunch/i/YnVtcGFuZGdyaW5k.mp3' handled. As you know, XBMC 12.0 was working fine with Rygel, but as you can see above, we now have the same "invalid seek request". Looking at post-release commits (https://github.com/xbmc/xbmc/commits/Frodo) I did not immedately spot the change that caused this. I will now do a Onkio pcap and send it in separate email. Do you want me to pcap XBMC too, or is it easier for you to pull XBMC 12.1 and have it running live on your side for testing? Thanks, Andrej Andrej Falout NZ: +64(21)02566825 AU: +61(45)1166010 US: +1(360)4880970 HR:+385(91)1520436 On Wed, Apr 3, 2013 at 2:43 AM, Jens Georg <[email protected]> wrote: > On Sa, 2013-03-30 at 13:31 +1300, Andrej Falout wrote: > > > > > By "description files" do you mean "configuration files" or > > something > > > else? > > > > > > The files in ~/.config/Rygel. Isolation works by > > > > a) Making sure you're not on a DBus session bus, otherwise new > > instances > > of rygel will stop the old ones (unsetting > > DBUS_SESSION_BUS_ADDRESS) > > > > > > If it refers to the shell environment variable, this is not set on my > > Fedora 16 installation: > > > > > > 1) Which app is expected to set this? > > The thing that starts your "session"; this might be systemd's user > session, the login manager, ... but on headless sessions it's usually > not set at all. > > > 2) If I understood correctly, all I need to do is to make sure this > > env var is empty? > > Yes. > > > > > > > b) exporting XDG_CONFIG_HOME to something different for each > > instance. > > > > > > This is not set on my machine either: > > > > 1) Which app is expected to set this? > > 2) I assume this needs to be set to a directory path? > > This is not meant to be set, the environment variable is used to > override the default from the standard. And yes, it's a path. > > > > >
_______________________________________________ rygel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/rygel-list
