- This topic has 6 replies, 3 voices, and was last updated Oct 8-11:15 pm by DaveW.
-
Posts
-
DaveW
Hi. I have Seamonkey 2.53.4, running on Antix 17.4, 32 bit.
It works well, except when I print a page (using Page Preview) the page footer (or header) Date/Time shows 12/31/69, and the time is arbitrary.
The correct date is shown in Seamonkey Preferences – Calendar – Date Text Format window: “Long: Tuesday, October 6, 2020”.
The Timezone is correct in Seamonkey Preferences – Calendar.The computer is showing the correct date/time, in the bar at screen bottom.
Seamonkey appears to know the correct date/time, but the info does not get transferred to the Print Page footer or header.I also have Firefox and Thunderbird on the system. Both of those handle date and time properly. Firefox prints the correct date/time on the page.
I first noticed this issue, yesterday, with Seamonkey version 2.53.3, and upgraded to 2.53.4, with no change to the problem. However, several months ago, with an earlier SM version the date/time printed properly. Of course, there have been other system upgrades since then, so I can’t tag this to a SM version.
Where would you look for the snag?
Thanks!- This topic was modified 2 years, 7 months ago by DaveW. Reason: misspelled word
Anonymous
not a seamonkey user, but I seem to recall the prefs are similar or identical across ‘zilla applications.
about:config
print.print_footerleft
print.print_footercenter
print.print_footerright
print.print_headerleft
print.print_headercenter
print.print_headerrightIn the past, I have emptied (made blank) the values for each of these in order to avoid printing headerfootercrap
&T &D should instruct where to print the time and the date.
Maybe your config contains a stray value for one of the print prefkeys?skidoo,
Your thoughts are much appreciated. I checked about:config and found the print.print_xxxx settings as they should be. The page header and footer settings are also selectable under Print Preview – Print – Options – Header and Footer.However, to be sure, in about:config, I experimented with the entries (deleted &D, tried it in another location, entered &T, etc.), each time checking the effect in the print preview. Wherever &D is placed, the date is 12/31/69, and the time is arbitrary. (By the way, &T is “Page Title”. &D appears to include date and time.)
I scanned through about:config, looking for lines that might affect the date source. Nothing lept out at me. But the answer may be in there somewhere.
Thank you!
ile
Hello DaveW aka tbwdave
found this at seamonkey project. Your question provided hours of reading about Unix Epoch zero or empty values., and 32bit mozilla for ff version 60+.
“SeaMonkey now uses a new api for formatting regional data like time and date. Default is to use the application locale of the current SeaMonkey build. If you use a language pack or a different OS formatting this is usually not desired. You can change the formatting from the application locale to the regional settings locale (OS) in the preferences dialog under “Appearance”. ”
It will be great if simply putting the bullet set to regional fixes it. most interesting that it is reported as working in Windows.
ile,
Thanks for researching the issue!Unfortunately, the problem was not fixed by changing to “Regional Settings Locale: English (United States)”, and restarting Seamonkey.
However, in Help – Troubleshooting, I see the Mozilla Location Service Key is “missing” (the Google Location Service, and Google SafeBrowsing keys are both “found”). I really don’t know what those are for (they sound like security concerns to me). But I wonder if the “missing” key could be a factor? If so, how does one make it “found”?
ile
Hello DaveW Okay You got me. seamonkey on mx19_32 and we are on the same day as you 12/31/69 &D print date. On seamonkey on mx19_64 the &D prints today’s Date/Time.
ile,
Thanks for confirming that the problem exists on your 32 bit MX system (not on 64 bit).I followed another rabbit trail, and found that FireFox v.53 had a similar problem a couple of years back (see
https://bugzilla.mozilla.org/show_bug.cgi?id=1362817).That thread seems to be a discussion between developers as they figured out the cause, which affects 32 bit systems only (which is also true of my present problem). I’m not bright enough to know whether the solution they found can be applied to my present SeaMonkey version, or if I must patiently wait for it to be fixed (hopefully) with the next update.
- This reply was modified 2 years, 7 months ago by DaveW. Reason: misspelling
- You must be logged in to reply to this topic.
