Can we sticky this thread please, because of the importance of this topic? (At least until this update business is resolved by a general consensus of the community and to the OP's satisfaction?) Thanks!
Post's in here keep it visible. Sticky isn't needed. IMHO
I totally agree with Bob. This thread is getting too long as it is and perhaps could have been made into a poll to shorten it, but too late now.
Being the OP of this long topic, I'd like to comment on some of the posts here.
About sticking this topic, I agree this is not really needed. Most users won't want to read so many posts in one topic. Moreover, I have already seen at least 2 additional topics around this same issue (
tray notifications), which gives more opportunities for the people of Avast to see this issue.
In theory, it would be useful to have all those topics concentrated in only one, but clearly Avast Team is not interested in commenting/posting/reading a long topic like this one. So at least they are providing useful info in those other topics.
About this topic being (too) long, I also agree. But the reason is that most of the first posts/pages were related to somehow "convince" frequent users to test this issue, or even to consider it "an issue".
I can count less than 10 posts really providing useful info / feedback / testing.
In addition, frequent forum users that participated in this topic could had potentially tested the problem when the latest stable release was out, but instead they decided to discared it and go ahead with the manual program update (which means that the program update tray notification would never be displayed anyway, and the inconsistencies would never be discovered). Of course that's their prerogative, but if more frequent users would had tested the issue and would had came here to report their findings, this topic would have been shorter, and it would have contribute much more in the effective solving of the problem.
I also want to comment on what is the "real" problem. *I* don't have a problem. *I* can manually update the program, no matter if the
incorrect tray notification shows up, or if no notification is displayed at all.
We have already reports of users saying that the program is not being updated, and *that* is already happening to some millions of Avast users. Of course I don't know about the real statistics coming from Avast's Servers. But just imagine say 10% of "normal" users not receiving program update tray notifications and not opening the GUI. Even with 1% or users, you would be already in the "million" order of magnitude.
Besides the program update tray notifications, we now know that there are some inconsistencies around this issue. As already explained, some users are seeing 2 tray notifications simultaneously, some 1, some the other, some none, and some users are waiting for automatic program update (instead of the default "ask") and that's NOT happening either.Should I mention also the yellow exclamation mark that
DavidR says it should be there, but never shows up? (Once again, *I* personally don't need it and don't even want it, but, should it be there or not?)
So, although I do
NOT think this topic needs to be a sticky, I indeed think that
Avast Team MUST take care of this problem
ASAP.
From what
Vlk commented in other topic, it seems that the distribution cycle takes 2 months.
First, the cycle relates to whether a program update tray notification shows up and when, but it doesn't explain all those inconsistencies.
Second, in less than (the last) 6 months, which would be somehow "equivalent" to 3 complete cycles, we had the stable releases of:
5.1.864
5.1.889
6.0.1000
6.0.1091
6.0.1125
(more than 3 stable releases). So I guess this is
part of the problem. So maybe the complete distribution cycle should be shorter, until the stable releases are "more stable"? It is also possible this absent of tray notifications is part of the testing / distribution strategies and techniques. If that's the case, simply come here and tell us. We'll receive it as known fact, instead of being a "problem".
Still, the 2 months cycle does NOT answer
all the inconsistencies.
Now, about being "too late" to make a poll, we could still open a new topic, with a simple explanation, the request to test the tray notifications
while waiting for a program update, and report it in the poll. Add a link to some of the topics talking about the issue, open the poll to more than one vote per user, and make *that* poll a sticky so more users would see it during the next, say, 3 months after the next stable release (more than one cycle).
Just the same as requesting translations, Avast Team could make a sticky poll, requesting to test tray notifications while waiting for an available program update. The poll could include all the several behaviours we have already described here in this topic, and even include the behaviours while selecting "automatic program update" (which
seems to be also "failing", as shown in some other topics).
We could still keep receiving comments here, reports, questions, and other not-so-relevant posts too

. The reality is that until and unless the people of
Avast Team (that take care of Servers and distributions) won't double check their systems, won't recheck the discrepancies with Avast's devs, and won't come here (or some other new cleaner topic) to talk with the users about this issue (meaning, specifically requesting from frequent users and beta testers to test it), we will keep "talking", and no real solution would be achieve.
Although this topic (and several of my own posts

) is already "too long", I hope other users come here to report. If they open additional topics about the same issue, although not ideal, it would be useful too.
If there is an interest of opening a new poll and making it a sticky, I'll be happy to discuss it here (in this long "dirty" topic), so the poll would be "clean and simple" but effective so it would be useful FOR AVAST TEAM.
@
AVAST TEAM, it is time (after several months of inconsistencies in this matter) that
YOU double check this issue

, with or without polls/stickies/topics/bug tickets.