This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
1LucindaLibri
I keep getting an error saying there's a problem with my system clock that is preventing you from setting cookies . . . pretty sure my clock is fine. And you are in my list of favorite cookies which are retained when I close my browser (not something I do for just anyone :)
Then when I go to login, AGAIN, the login boxes aren't there. I have to click on one of the other buttons at which point the page with the login boxes loads . . .
Safari 4.1.2 MacOS 10.4.11
Then when I go to login, AGAIN, the login boxes aren't there. I have to click on one of the other buttons at which point the page with the login boxes loads . . .
Safari 4.1.2 MacOS 10.4.11
2brightcopy
1> Can you verify both that your system clock is correct AND that your timezone is set correctly?
3LucindaLibri
yes
4brightcopy
Sorry, I should have also asked that the DATE is correct as well (rather than just the time, aka "clock").
5LucindaLibri
yes yes yes
I used the System Pref Panel to resync the date & clock automatically with time.apple.com and checked the time zone. All are good.
I used the System Pref Panel to resync the date & clock automatically with time.apple.com and checked the time zone. All are good.
6brightcopy
5> Could you go back and check them again? Cause it would REALLY help solve the problem if it was that. ;)
Just kidding. Hmm, well, when you get this error, is it an actual LT webpage that comes up? Can you post the URL or a screenshot of it? Or is it a browser popup window?
Just kidding. Hmm, well, when you get this error, is it an actual LT webpage that comes up? Can you post the URL or a screenshot of it? Or is it a browser popup window?
7LucindaLibri
Yes, it was an LT page, not a popup . . . at least it had the LT header.
I think it had "&problem9" somewhere in the url, though it seems to be fixed now . . .
If it happens again, I'll capture it for you.
Thanks.
I think it had "&problem9" somewhere in the url, though it seems to be fixed now . . .
If it happens again, I'll capture it for you.
Thanks.
8brightcopy
Marking it as closed. But if it comes up again, just post and change the bug status to Needs Discussion.

