[mythtv-users] Frontend submits hardware profile every startup

Thomas Mashos thomas at mashos.com
Mon Jul 9 13:07:32 UTC 2012


On Mon, Jul 9, 2012 at 1:38 AM, John Veness
<John.Veness.mythtv at pelago.org.uk> wrote:
> On 15/06/2012 11:15, John Veness wrote:
>>
>> Hi,
>>
>> My mythfrontend seems to be submitting a hardware profile every time it
>> starts up. The relevant part of mythfrontend --v all would seem to be:
>>
>> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
>> hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was
>>  > 30 days ago, update required...
>> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
>> mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
>> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext
>> system-unix.cpp:735 (Fork) - Managed child (PID: 22471) has started! *
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>> -a, timeout=0
>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>> -a, status=256, result=1
>>
>> As you'll see from the timestamps, this adds a 45-second or so delay to
>> mythfrontend starting up, during which time it looks like it's hung.
>>
>> Any ideas why it's doing this every time? It looks from the log like it
>> should only be doing this every 30 days.
>>
>> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
>> this problem for the last week or two.
>>
>> Cheers,
>>
>> John
>
>
> Further to this, setting a PIN didn't make a difference. Eventually I
> deleted (well, renamed just in case) the folder ~/.mythtv/HardwareProfile
> and that has got rid of the delay so I assume it isn't submitting the
> hardware profile every startup. I'll keep an eye on it.
>
> Does anyone want to see the previous contents of the HardwareProfile folder
> in case that helps them troubleshoot what the problem was?
>
> Cheers,
>
> John
> --
> John Veness, MythTV user, UK, DVB-T
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

If you are using Mythbuntu and submitting the Whoopsie report then the
issue is that sendprofile.py cannot reach your backend, as that is
what all of the whoopsie reports for sendprofile.py have been for the
last month. If you aren't using Ubuntu and/or aren't submitting the
whoopsie report then I don't know what the issue is. I think it's
probably safe to say that it isn't submitting the hardware profile
every time, but rather failing to send the hardware profile and thus
trying to send it every time.

Thanks,

Thomas Mashos


More information about the mythtv-users mailing list