The problem
I want to point to all forum users that the issue was not appeared for me. But if I post such info, it will flood or even spam the thread (imagine many users posts: some “not for me”, some “me too”).
If users can’t vote, we don’t know an issue share - how wide is it: is it user-specific case or is the case has wider share among other forum users.
The possible solution
If I have the same issue, but I don’t have any additional payload info, theoretically I could vote for it “me too”, so I have the same issue.
And in opposite way: If I did the same but have no such issue I can vote “not for me” or “I don’t have it”.
So I suggest to add a block with vote poll with 2 options: “have the same” and “have no such issue”.
Benefits
We all can see how “massive” the issue is - what an issue share among users is - what auditory it covers. We can note is an issue is user specific case or has some other users who met the same issue also.
So vote poll can help to classify an issue: user specific or an issue has a wide share.
Further idea development: you can add personal or team forum or email or a messenger notifications for example 3+ or 4+ or 5+ votes to get to know massive problems earlier than just surfing around the forum and to have no idea how “massive” an issue is.
Note
May be to describe the same behaviour is not suitable for other forum users and it could flood a thread with useless info also. Showing a voting poll can fix it.
PS
Initially inspired be the post [Unstable Update] June 2026 - #26 by jrichard326 cause I have the same issue but don’t want to flood a thread with mine “me too” post without any other payload info.
Yes it is another case - not a dedicated thread, but just post in it. But a start of the idea implementation could be separate dedicated topics - at least in the beginning as initial and main step forward.
IMHO this doesn’t give anything back to the community, it promotes a quick interaction rather than troubleshooting an issue. If you think you have the same issue as someone else, the least you should be doing is proving it by providing system specs and logs so the source of the problem can be identified and bug reports submitted or solutions provided. Just saying “me too” likely gives false numbers of people having the same problem and puts all the effort for a solution onto the original reporter and anyone trying to troubleshoot it. This goes triple for anyone on testing or unstable branches where the expectation is that you do some troubleshooting yourself rather than relying on the community to fix things for you.
Here on the Manjaro forum, support threads are intended for support—meaning they usually focus on helping a single user with a specific problem.
This process typically involves a series of questions and answers tailored to that specific system configuration.
If others encounter the same (or a similar) issue, we generally encourage them not to jump into the original thread, but rather to start their own support thread.
In our experience, it is rare for the underlying cause or the effective fix to be identical across different cases.
Therefore, we believe it is best to thoroughly address the initial thread so that a solution can be found; this yields the greatest benefit for everyone.
A poll does not contribute to a solution
instead, it either creates unnecessary pressure
or leads to a person’s problems being devalued through negative ratings.
Edit:
And now, to wrap things up, please take another look at the thread you cited as an example. I’m bringing it up now as a real-life illustration of why that poll idea really isn’t a good one for our forum. And take a look at the solution.
I think this quote is one good of endless examples where some people point at:“We having a really big problem here.”
Where at the end, the user forget about his individual adjustment which has no compatibility and is highly experimental… it happend to me also and its normal to forget about it.
People should always write their own OS Modification.txt where he/she documented all changes and adjustment which he has made for program’s and the OS itself, otherwise we run into drama which maybe could easily be evaded.
andreas85, that’s what I meant when suggested the opposite button “I not have this issue” and in that particular thread you suggest me to check, I would press such button to illuminate that user’s case it not so widely shared as, for example, the linux 7.1.1-1 package case, where perhaps every user met a problem booting their PC.
So if we talk about whole idea, after analysing one branch “me too”, please do not forget to get back to the branching point and to check another branch “I hadn’t that problem”. So we could have a stats “me too” and to compare it against “in my case it works well”.
IDK, I agree that single btn “me too” looks weird, but if to provide a choice with the second option in conjunction with the first button, then perhaps it could be useful. I think we can’t say exactly is it good or poor idea until we did not try it in practice. I don’t have strong opinion that I am completely wrong or my opponents completely wrong I just thought it could be good to try.
Forgive me if I sound blunt — I don’t mean to be — but you seem to be under the impression that this forum would be a corporate support ticket system. It’s not. We are using Discourse as the back-end here, and Discourse is merely a forum engine.
As such, what you are suggesting is technically not even feasible, because it would require subthreads, which Discourse does not support.
The most important stuff is already said, but my 2 cents.
“i do not have it” is per se the default. Most of the problems are individual ones. Such button will only make sense if coupled with extensive telemetry, which is not the case here. So we still hope that the user posts his inxi…properly formatted of course
At least 10 people are reading all the new topics. And the update one. The last time there was a common problem (even though it affected a fraction of the users) - the mesa one, we noticed at about the 3rd similar topic, about a day later with the help of a user a workaround was found and published in the “known problems”. So, the summarization if there is indeed a globall-ish problem already works nice.
To sum up: “i have it” - has limited value as only 1 button without user machine information, when such is provided in a separate topic , we analyze and summarize.
“i do not have it” makes no sense since it is the default stance.
Somewhat grey zone is the update topic, where small comments like this or small problems are somewhat tolerated, if we see a separation in a new topic is needed we do this.
You can use a or to indicate you have the same issue (hover over the heart on the post and select the emoji you want). Alternatively just wait for a solution to be found (and/or keep searching).
Better yet open your own thread and provide information.
I just thought it could be good to try.
or 
to indicate you have the same issue (hover over the heart on the post and select the emoji you want). Alternatively just wait for a solution to be found (and/or keep searching).