[mythtv-users] Frontend submits hardware profile every startup

[Thomas Mashos]

On Mon, Jul 9, 2012 at 6:18 AM, John Veness
<John.Veness.mythtv at pelago.org.uk> wrote:
> On 09/07/2012 14:07, Thomas Mashos wrote:
>>
>> 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.
>
>
> Hi Thomas,
>
> I'm running Ubuntu with 0.25-fixes from your mythbuntu repos, which I assume
> is close enough to what you're talking about. The machine in question is a
> combined FE/BE and works fine in general, other than this mythfrontend
> startup delay. I don't know what a Whoopsie report is.
>
> If you can tell me what to type to troubleshoot whether sendprofile.py can
> or cannot reach the backend, or whatever other troubleshooting you wish me
> to try, then let me know.
>
> 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

A whoopsie report is when the dialog box pops up and says that
something has stopped working and asks you to send information to the
ubuntu developers. A better/fuller explanation can be found in the
first answer here

http://askubuntu.com/questions/135540/what-is-the-whoopsie-process-and-how-can-i-remove-it

The error report it sends is attached to a guid rather than any
identifiable information. I'm looking to see if that guid is kept
anywhere on the system for you to find. If it is and you tell me what
it is I can look up your specific error report and see the exact error
message (although all of them are backend connectivity issues).

You might also want to see if there are any files in /var/crash/

Thanks,

Thomas Mashos