Our lives don’t depend on it.
There is no need for an urgent response to this.
Ehh there kind of is. Software bugs don’t happen in a vacuum independent of each other, and New_Style_xd found at least three when he installed the new version (albeit one of them being on the old version for some users too), so that could suggest some instability or other more serious issues with this new version that was, by the way, released to the public. We’re not talking about a Beta here. It’s also more than a little bit concerning that the new version is as buggy as it is after they went through many beta versions and more than in any previous version in a while.
So, yeah, I would like to know if they’re at least investigating them and will release a fix for them at some point along the way.
Thank you friend. I agree with you.
I’m starting to think that the avast beta testers aren’t testing anything… lol
For a product that has been in testing for a long time, and no one has said anything about the bugs that have been presented until now, this is very strange.
It won’t be long before someone arrives here and says the old MANTRA telling me to remove and install Avast again, then I’ll smile a lot…
It will seem like not even computer technicians, if there is a problem with the computer, they will format the computer and that will solve it.
We’re talking about a seriously big project. which has been there since 1988.
People are thinking that business is a joke.
Just FYI there was a typo in my post that you quoted. I fixed it though.
Okay, I made the comment after you corrected it
I totally agree, the degree of the problem would impact the urgency of response. e.g. does it impact on the protection provided by Avast.
It would also be down to the number of people actually effected. I haven’t seen it in either 23.12 or 24.1, so how widespread it is we simply don’t know.
I certainly wouldn’t put this issue in that area.
Please note that the newest version on the Menu>Settings>Update page is identical to the one found on Menu>About page.
I have not updated yet because full offline installer has not been deployed for version 24.1.
See attached below for particulars:
Alert History unaffected and does not display either 19 or 20 January 1970 dates.
New thread for 24.1 version here: https://forum.avast.com/index.php?topic=326107.msg1714423#msg1714423
Now 11:40 pm 2/8/2024 in the States at this time… couple of days late.
the wrong date format will be fixed in next UI release.
Thanks for the update Petr
As for me, I have also been affected with the 1970 bug before updating and still on 23.12. Maybe it’s a slow moving crawl that gets us all eventually.
Good to know that it will be updated in the next version of the UI.
Now why was it affected in version 23.12?
This is our doubt because there are many people who are on version 23.12.
Where are these ‘many’ effected ?
They certainly aren’t here in their droves. For the most part many don’t take regular excursions into the UI.
There are several here on the forum.
Just look at the launch and other topics, there are always people talking about it.
It’s likely the UI version, which you can see from the About page. The UI version updates independently of the program version (though sometimes with a new program version comes a new UI version), and that UI version could be buggy. Just an educated guess though.
Thank you great friend.
I now see my UI, it is updated. even though I have version 23.12.
Several on the forums out of hundreds of millions of Avast users, can you not see the difference between a few in the forums.
True, I agree with you. Even so, it’s still a bug. whether he is critical or not. the problem exists.
Do the math here.
There are less than 15 active/regular posters on this forum even if we include Avast staff, and at least four or five have pointed out that they are experiencing this bug. Law of averages would tell us that the bug is affecting many many more users even if the average user doesn’t ever open up their UI to look at anything, let alone the notifications, let alone the timestamp on said notifications.
A bug is a bug is a bug, regardless of how many people it’s affecting and how many people are actively noticing it.
If you want to argue that the severity of the bug means it shouldn’t be treated with the highest priority (which no one is advocating for, to be clear. Just that it be acknowledged, which it was), then that’s a different stance that I could agree with. But the number of people who pointed out the bug should be irrelevant.
I completely agree with you my friend.
We are always here on the forum, trying to report and help people, when we talk about the bug, the vast majority ignore the case, saying that the bug is not for everyone and others.
Guys, whether the bug is big or small, you always have to take a good look at what we’re doing here.
I’m thinking they don’t see other forums. The business in the other Kaspersky forums, Eset the neogene is catching fire. staff treat what we report with great relevance.
Same here, 24.1 version.
I saw the problem when Avast threw a blue ball in systray, saying I have a notification. I wasn’t in front of the computer for an hour so I went to see what is it and I have no idea if it was something from history or actually new blocked threat because date is 20 jan 1970 and time is completely wrong and not working.
Now I have no idea what the notifiaction was about. So yeah, it is a problem.