Apparently the discovery process gets stuck then. Can you run it
inside gdb and
get a "thread apply all bt" output? Thanks.
Maybe I'm being dense, but if rygel does not crash, how can I get a
"thread apply all bt" output?
Just CTRL-C (aka send SIGINT) it.
Also just do gdb on mx-extract, so:
gdb --args /usr/local/libexec/mx-extract --extract-metadata
EXTRACT file:///....
then CTRL-C
and t a a bt
Also try using GST_DEBUG=*iscover*:7,*:2
$ GST_DEBUG=*iscover*:7,*:2 rygel
Rygel-Message: rygel-acl.vala:143: No ACL fallback policy found. Using
"allow"
Rygel-Message: Rygel v0.32.1 starting?
RygelCore-Message: New plugin 'MediaExport' available
MediaExport-Message: rygel-media-export-extract.vala:163: Started with
descriptors 3 (in) 4 (out)
MediaExport-Message: 'file:///home/tc/Pictures' harvested
MediaExport-Message: rygel-media-export-harvesting-task.vala:300:
Harvesting of file:///home/tc/Pictures done in 0.096817
MediaExport-Message: rygel-media-export-extract.vala:163: Started with
descriptors 3 (in) 4 (out)
MediaExport-Message: rygel-media-export-extract.vala:163: Started with
descriptors 3 (in) 4 (out)
0:00:00.102207708 10927 0x13be180 WARN discoverer
gstdiscoverer.c:1612:start_discovering: No URI to process
0:00:00.101578125 10928 0x14c3180 WARN discoverer
gstdiscoverer.c:1612:start_discovering: No URI to process
MediaExport-Message: rygel-media-export-extract.vala:163: Started with
descriptors 3 (in) 4 (out)
0:00:00.120645261 10926 0x3d6180 WARN discoverer
gstdiscoverer.c:1612:start_discovering: No URI to process
Ok, not really helpful... very odd.
_______________________________________________
rygel-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/rygel-list
