[SOLVED] Wrong Year Displayed in Clock
[SOLVED] Wrong Year Displayed in Clock
Hello All,
Started up MX-18 this morning & noticed the Clock seems to be a year ahead of itself, showing 2019 instead of 2018.
When clicked the calendar still shows 2018.
Logout, restart doesn't fix it
Started up MX-18 this morning & noticed the Clock seems to be a year ahead of itself, showing 2019 instead of 2018.
When clicked the calendar still shows 2018.
Logout, restart doesn't fix it
You do not have the required permissions to view the files attached to this post.
Last edited by JmaCWQ on Mon Dec 31, 2018 9:53 pm, edited 1 time in total.
- Gordon Cooper
- Posts: 965
- Joined: Mon Nov 21, 2011 5:50 pm
Re: Wrong Year Displayed in Clock
Orage clock is correct here.
Backup: Dell9010, MX-19_B2, Win7, 120 SSD, WD 232GIB HD, 4GB RAM
Primary :Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
MX-18.2 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.
Primary :Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
MX-18.2 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.
Re: Wrong Year Displayed in Clock
I'm not certain but IIRC there is a strange problem with orage and timezones. There is a system-wide timezone setting that IMO is the only one that should be used although it requires root privileges. Then orage has a separate timezone setting for each user. Perhaps this or something like it is causing the problem.
@JmaCWQ, you can probably check this by running the "date" command in a terminal window. If that gives the correct answer then the problem probably lies in some orage settings. If there is an orage config file maybe you could try deleting it (or safer: rename it) and see if that fixes the problem.
@JmaCWQ, you can probably check this by running the "date" command in a terminal window. If that gives the correct answer then the problem probably lies in some orage settings. If there is an orage config file maybe you could try deleting it (or safer: rename it) and see if that fixes the problem.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
Re: Wrong Year Displayed in Clock
Thanks for the replies.
Timezone is Australia/Brisbane.
Running date in Terminal shows correctly:
Both the Xfce panel clock (OP image) & the Date/Time plugin's clock show this error, not sure about Orage, it's panel clock seems to ignore any strftime changes I make in line 1 or the tooltip line in it's properties, and it's default tooltip shows 'Monday 31 December 2018/01', which is the wrong week number.
If I change either of those lines & click Close it ignores the changes & when properties is opened again they show unchanged from default.
In ~/.config/orage there's a file oragerc, renaming or deleting it does nothing after logging out & back in again.
But anyway, I'll be sticking with the Xfce panel clock and I'm not bothered by it displaying the new year a day early, thought it was maybe an issue affecting others also.
Will see what happens after midnight if it stays at 2019 or changes to 2020
Timezone is Australia/Brisbane.
Running date in Terminal shows correctly:
Code: Select all
$ date
Mon 31 Dec 16:42:57 AEST 2018
If I change either of those lines & click Close it ignores the changes & when properties is opened again they show unchanged from default.
In ~/.config/orage there's a file oragerc, renaming or deleting it does nothing after logging out & back in again.
But anyway, I'll be sticking with the Xfce panel clock and I'm not bothered by it displaying the new year a day early, thought it was maybe an issue affecting others also.
Will see what happens after midnight if it stays at 2019 or changes to 2020
Re: Wrong Year Displayed in Clock
I't will happen again. Nothing to worrie about, B/c it's just a definition issue of what you are going to display:
Have a look at this:
Code: Select all
date +'Date %%d.%%m.%%Y %d.%m.%Y:'
date +'ISO-Year/week (01..53 - mon-sun) %%G %%V: %G %V'
date +'normal Year/Week (0..53 sun-sat) %%Y %%U: %Y %U '
date +'normal Year/Week (0..53 mon-sun) %%Y %%W: %Y %W '
Code: Select all
Date %d.%m.%Y 31.12.2018:
ISO-Year/week (01..53 - mon-sun) %G %V: 2019 01
normal Year/Week (0..53 sun-sat) %Y %U: 2018 52
normal Year/Week (0..53 mon-sun) %Y %W: 2018 53
And confusingly together the normal year combined with the ISO-week.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Wrong Year Displayed in Clock
Shoot, I thought it was like me... I catch up with year number sometime around June each year.
Happy New Year, whatever the number.
Happy New Year, whatever the number.
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Re: Wrong Year Displayed in Clock
The year displayed stayed at 2019 after midnight by the looks of things, it must have just decided it wanted to switch to 2019 a little early to avoid the hangover or something....or the more logical answer, it was because I mistakenly used %G instead of %Y to display the year
The combination I was using, which gives the display as pictured in the first post:
Which I've changed to:
Now I just have to wait a year to see if the change brings the desired results
Code: Select all
%A %n %B %d, %G
Code: Select all
%A locale's full weekday name (e.g., Sunday)
%n a newline
%B locale's full month name (e.g., January)
%d day of month (e.g, 01)
%G year of ISO week number (see %V); normally useful only with %V
Code: Select all
%A %n %B %d, %Y
- Eadwine Rose
- Administrator
- Posts: 11968
- Joined: Wed Jul 12, 2006 2:10 am
Re: Wrong Year Displayed in Clock
Not on topic, but this bit tickled my funny bone heheh.JmaCWQ wrote: ↑Mon Dec 31, 2018 9:52 pm The year displayed stayed at 2019 after midnight by the looks of things, it must have just decided it wanted to switch to 2019 a little early to avoid the hangover or something....or the more logical answer, it was because I mistakenly used %G instead of %Y to display the year
I was wondering what would happen to that year. :)
MX-23.2_x64 July 31 2023 * 6.1.0-20-amd64 ext4 Xfce 4.18.1 * 8core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 525.147.05 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Wrong Year Displayed in Clock
A day without laughter is a day wasted - Charlie ChaplinEadwine Rose wrote: ↑Tue Jan 01, 2019 6:13 am Not on topic, but this bit tickled my funny bone heheh.
I was wondering what would happen to that year. :)
Re: [SOLVED] Wrong Year Displayed in Clock
Could be the 'Happy New Year 2018!' bug that hit Sydney
https://www.abc.net.au/news/2019-01-01/ ... e/10676974
https://www.abc.net.au/news/2019-01-01/ ... e/10676974
Inspiron 15 5000-5593- (i7-1065G7) MX 23..2 AHS/MX-21//W10 - Lenovo ThinkCentre A58 4GBRAM (64-bit), MX-23.2/MX21.3./antiX 23/Mint 21.3, Ubuntu 22.04.4, openSUSE Tumbleweed,