[mythtv-users] time zone with distant frontend

Johnny Walker johnnyjboss at gmail.com
Sun Jan 31 22:34:20 UTC 2010


On Sun, Jan 31, 2010 at 3:12 PM, Johnny Walker <johnnyjboss at gmail.com> wrote:
> On Sat, Jan 23, 2010 at 8:27 PM, Michael T. Dean
> <mtdean at thirdcontact.com> wrote:
>> On 01/23/2010 06:45 PM, Johnny Walker wrote:
>>> On Tue, Dec 29, 2009 at 3:38 PM, Michael T. Dean wrote:
>>>
>>>> On 12/29/2009 12:34 PM, Johnny Walker wrote:
>>>>
>>>>> On Tue, Dec 29, 2009 at 11:30 AM, mythtv-free wrote:
>>>>>
>>>>>> I got this message from my mythtv:
>>>>>> "Time zone settings on the master backend differ from those on this
>>>>>> system.
>>>>>> 2009-12-29 18:23:15.291 Detected time zone settings:
>>>>>>   Master: Zone ID: 'CET', UTC Offset: '3600', Current Time:
>>>>>> '2009-12-29T18:23:15'
>>>>>>    Local: Zone ID: 'Europe/Paris', UTC Offset: '3600', Current Time:
>>>>>> '2009-12-29T18:23:15'
>>>>>>
>>>>>> 2009-12-29 18:23:15.291 The time and/or time zone settings on this
>>>>>> system do not match those in use on the master backend. Please ensure
>>>>>> all frontend and backend systems are configured to use the same time
>>>>>> zone and have the current time properly set.
>>>>>> 2009-12-29 18:23:15.292 Unable to run with invalid time settings.
>>>>>> Exiting.
>>>>>> "
>>>>>> I think that this time checking is too sensitive! Is it new in 0.22 ?
>>>>>>
>>>>> My feeling is that a pop-up is warranted to at least tell you. In many
>>>>> cases you're auto-starting the mythfrontend and all that happens is
>>>>> that it crashes back to desktop.
>>>>>
>>>> It doesn't crash.  It does exit.  It also explains why it's doing so in the
>>>> log messages that are quoted above
>>>>> I bet I could figure out enough C to make a dialog box happen. You'd
>>>>> still wind up having to connect to keyboard or SSH in to fix it but at
>>>>> least the error would be more friendly.
>>>>>
>>>> That would be appreciated.
>>>>
>>> I've finally found time enough to get cracking on this and it's almost
>>> working. Is there a preference of using MythDialogBox over
>>> MythPopupBox since the former is libmythui which, I believe, is the
>>> direction new code is supposed to be moving, or does it matter much?
>>>
>>
>> Things are going the MythUI way and new non-mythui stuff is no longer
>> being accepted, so you do want to go the mythui way...  I can't tell you
>> for sure which is that way, though--you seem to know that better than I.
>>
>> Mike
>>
> I have a friendlier error message using MythConfirmationDialog working
> now for the .22 fixes branch. How do I go about submitting it? Create
> a ticket for it?
>
> -JohnnyJboss
>
Here's the ticket with a diff attached to it.

http://svn.mythtv.org/trac/attachment/ticket/8004/

-JohnnyJboss


More information about the mythtv-users mailing list