[mythtv-users] uPnP - new problems in 0.27.2

John Pilkington J.Pilk at tesco.net
Fri Jul 4 09:26:17 UTC 2014


On 07/04/2014 09:20 AM, Jean-Yves Avenard wrote:
> On 4 July 2014 08:58, Ludvik Tesar <ludvik.tesar at gmail.com> wrote:
>
>> It seems the problem is that instead of correct port (which is 6544) there
>> is unicode character U+0090 in the soap response for UPnP. For example :
>> http://10.0.0.12:<U+0090>/Content/GetRecording?ChanId=1001&amp;StartTime=2014-07-03T21:20:00Z
>
> There were two issues at play, and I'm extremely sorry for not
> spotting the problem earlier :(
>
> First a typo that would cause GetBackendStatusPort to return not the
> status port (6544) but the control port(6543)
>
> And then, the function would return an int. The old code expected a
> string. The default QString constructor has a QChar paramater, which
> would convert the int into a UTF-16 char instead..
>
> I've pushed a fix, it should all be fine now in both master and
> fixes/0.27 and will tag a new 0.27.3 hoping that 0.27.2 will be
> forgotten quickly :(

Great.  Many thanks.  I'm glad we caught it quickly.  I'll probably let 
it settle for a few days before building again; other things to do :-)

John




More information about the mythtv-users mailing list