GNOME Bugzilla – Bug 749775
Transcoding/proxying of URLS with @ADDRESS@ does not work
Last modified: 2018-05-22 12:55:03 UTC
t-rygel:13378): MediaEngine-GStreamer-CRITICAL **: Error from pipeline RygelGstDataSource: gstsouphttpsrc.c(1491): gst_soup_http_src_parse_status (): /GstPipeline:RygelGstDataSource/GstSoupHTTPSrc:souphttpsrc0: Error resolving 'ADDRESS@': Name or service not known (2), URL: http://@ADDRESS@:4714/listen/source/alsa_output.pci-0000_00_1b.0.analog-stereo.monitor, Redirect to: (NULL)
I have the exact same problem. It has made rygel all but useless to me. All I wanted to do was serve pulseaudio as a dlna source. (rygel:31374): MediaEngine-GStreamer-CRITICAL **: Error from pipeline RygelGstDataSource: gstsouphttpsrc.c(1567): gst_soup_http_src_parse_status (): /GstPipeline:RygelGstDataSource/GstSoupHTTPSrc:souphttpsrc0: Error resolving 'ADDRESS@': Name or service not known (2), URL: http://@ADDRESS@:4714/listen/source/alsa_output.pci-0000_00_1b.0.analog-stereo.monitor, Redirect to: (NULL) (rygel:31374): RygelServer-WARNING **: rygel-http-request.vala:103: Byte seek not supported for http://192.168.2.29:40403/org.gnome.UPnP.MediaServer2.PulseAudio/i/L29yZy9nbm9tZS9VUG5QL01lZGlhU2VydmVyMi9QdWxzZUF1ZGlvL1NpbmtzLzA%3D/res/MP3.mp3
Second warning will need a fix in the device hacks, because your client is seeking where it shouldn't. Regarding the wiki, see https://wiki.gnome.org/QuickStart#OK.2C_I_have_an_account._Now_what.3F - Basically the whole wiki was set immutable b/c spam.
Er Comment 2 was for a different bug
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rygel/issues/89.