Date: Fri, 15 Jan 2016 09:24:06 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Guido Falsi <madpilot@freebsd.org> Cc: =?UTF-8?B?R2Vycml0IEvDvGhu?= <gerrit.kuehn@aei.mpg.de>, freebsd-net <freebsd-net@freebsd.org> Subject: Re: upnp/dlna Message-ID: <CA%2BtpaK0U%2BA--WnejtfTBGba066JiFM22s%2BsgM705m05HwqwsqQ@mail.gmail.com> In-Reply-To: <56990C36.2080207@FreeBSD.org> References: <20160115145225.e0dbde9632d5122df8acbb41@aei.mpg.de> <569905DA.2000903@FreeBSD.org> <20160115160020.e07e5a701b55a9a25b190278@aei.mpg.de> <56990C36.2080207@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 15, 2016 at 9:11 AM, Guido Falsi <madpilot@freebsd.org> wrote: > On 01/15/16 16:00, Gerrit K=C3=BChn wrote: > > On Fri, 15 Jan 2016 15:44:42 +0100 Guido Falsi <madpilot@FreeBSD.org> > > wrote about Re: upnp/dlna: > > > > GF> Could you try the patch here: > > GF> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205430 > > > > I'll try and report back, thanks for the pointer. > > > > GF> I think you're seeing that same issue. > > > > I did not look into the report too deeply (yet), but it looks like it i= s > > only referring to minidlna, and I see the same issue with mediatomb, to= o. > > But I'll need to find some more time over the weekend to look into this= , > > thanks again. > > > > Yes that bug is only about minidlna, I never used mediatomb and don't > know if thee issue there is related or not. > > The bug in minidlna was introduced upstream in the latest version, I > think it's caused by some API difference between FreeBSD and Linux. > > Maybe the mediatomb problem has a similar cause, and a similar fix can > be applied. > mediatomb works fine for me, 2 installs as the end of December. --=20 Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK0U%2BA--WnejtfTBGba066JiFM22s%2BsgM705m05HwqwsqQ>