Mods marking posts "solved" and locking?

I’ve used Manjaro for a long time on many PCs but I tend to only post issues on the forum as a last resort. Seems like everytime I do I wind up scratching my head as to why I bothered.

That’s nothing against anyone who posted some helpful hint towards a solution, there’s just always something odd about the way the post is handled.

I posted this about a week ago:

Someone had some suggestions but they were not what resolved the issue, the particular suggestion overlooked something about what I said in the first post. I wound up fixing it but it I was googling the issue alot and wasn’t quite sure what fixed it, and I mentioned that. It was likely to do with updating mirrors.

I did not check the post for a few days, I just checked it now. It has been marked with a solution and locked after only 3 days. That was NOT the solution and I wanted to respond to the comments about using pamac and “incomplete outputs”. I did use pacman, not pamac (as shown) and that was the full output, thinking that it was not was misunderstanding the problem.

So now you have a post marked solved with some conversation going on that had nothing to do with the issue and it’s locked, so it can’t be clarified. It really makes you think twice about coming across a post marked “solved” on this forum when you are looking for answers to a similar issue. I have no idea why there is such a hurry to mark a post and lock it.

I can’t say I’ve experienced this myself as I’ve probably asked less than a handful of “support” questions in my time on here, but it’s worth messaging a Moderator about a thread you started in which someone else marked a post as “Solution”?

I’ve only once (so far) marked a post as “Solution” on someone else’s thread after carefully reading the thread and it hadn’t been responded to in over a week, since said post was implied to be such, as far as I could tell. If I do so again, I’ll be sure write a comment saying why and to dispute it if appropriate; I think this should be the way to go. I’m not a Moderator, by the way.

This does seem a bit unfair though, in your case, but without reading some of these threads I can’t say for certain. Can you provide links to one or two of these? :wink:

Hope this helps? :smiley_cat:

3 Likes

Topic reopened and marked as unsolved.
Sometimes people like me “TL4” (and 70 users TL3 ?) or moderators mark a solution if we think the topic author forgot to do it…

And there are also misclicks; 2 or 3 times, my mouse slipped when I thought I was clicking on the heart.

8 Likes

That is quite easily done! I hope that an “un-select” would re-open the thread? In one case since it was a week or so “stale”, the thread was instantly closed.

Over the years we have seen a lot of spammers.

One of their preferred approaches are to comment on open topics - even though the topic is long dead - referred to as necro bumping and frowned upon.

Posting in old threads, or “necrobumping” is generally discouraged in the technical issue subforums, since it can potentially create disjointed “zombie” information; outdated posts with data which is no longer relevant due to Manjaro’s rolling nature, combined with more recent posts reflecting more current circumstance.
Forum Rules - Manjaro

To avoid such thing - threads that is marked with a solution - closes in three days.

That is how it is - some oppose to it - it should stay open forever if no solution - but that is a bad idea with a rolling release - if they were to stay open forever - then updates to the software in question may have solved it in the meantime - and thus the topic becomes irrelevant.

Which is why it autocloses when a solution is provided.

As for your specific topic see my comment - Cannot update, everything fails to satisfy dependencies - #14 by linux-aarhus on why you need to remove a custom package interfering with your sync.

4 Likes

No offense but I feel like you don’t spend enough time reading the topic you reply to. There is a link posted in this OP, and you’re actually the one that provided the solution I was talking about. I don’t know if maybe you’re accessing the forum with some device that makes it difficult to read the post, but it’s posted with a link directly to the topic I’m talking about.

Again, no offense but I’m looking at my original post and scratching my head like “but there is a link?”

Well there’s a big difference between forever and 3 days. Honestly I really don’t understand why people get upset about “necro-bumping” anyway. For example, one of my systems loses bluetooth after like 1/4 updates. Everytime it happens, I remember it happening before but I forget what fixed it. So I google and I always hit the same post that says to remove the bluetooth USB module and re-start it. Last night it happened again and I actually wanted to reply to that thread and say “this is still happening”. It’s like 2 years old so it’s locked. I could create a new thread just to say “hey this thing in this old thread is still happening”, but that’s probably less effective and the people involved in the original thread won’t be notified

Again, as I stated in that thread…it was every package. I was using the --ignore switch on the packages that were failing including the one I posted the example output. I even mentioned that qt5-tools was failing which is an official/extra. I understand what you are saying, sometimes I do have to remove AUR packages and reinstall them but I generally try ignoring the first few that fail to make sure that’s what I have to do, which is what I did there. The output I posted was probably not a good example as it confused the point, but I did iterate that it was ALL packages that were failing. I’ve been running AUR packages forever so it’s not the first time I’ve come across the issue you are mentioning but if that was the issue I would not have posted at all…because I’ve dealt with that many times.

More like my eyes, and constant distractions :smile_cat: … no worries.

I regularly post on the Forum in a public environment (at the Pub); quite easy to get “conversation-bombed” in the middle of composing a post, or at home, my cat is not the quietest of companions … he’s been badgering me non-stop since his sister passed away last year.

My impression from your post was that someone else had marked it as a “solution”. If you think it is, feel free to do so again, but that will lead to the thread being closed, which you apparently didn’t want.

Hope this clears things up a bit (preferably my eyes, too!)

If a question has an answer, but there are follow-up questions, it’s best to start a new thread for those and link to the original thread.

All the best!

Well the big point of this post was I don’t understand why even if there is a solution locking the thread after 3 days maybe isn’t the greatest idea.

If that’s the way the forum operates then that’s just how it is. “Necro-bumping” I suppose is the concern here but sometimes Necro-bumping is constructive…here’s an example…

I posted this question on the Manjaro forum recently…

I have had this problem forever on this machine, and I decided to try to fix it again. My assumption was it always had something to do with Plasma or Gnome or Manjaro, then as I marked in that solution, I came across this post on Level1techs

I necro-bumped that thread just to say “hey this worked for me too”. Out of millions of monitors on the market, I can’t be one of 2 people who have had this issue and runs Linux. Even tho the thread is 1.5 years old, it’s still a valid fix. It’s a little easier to find if someone confirms it as a fix.

1 Like

I’ll drop this here for consideration;

You really don’t have to understand it. So-called necro-bumping isn’t desired in this (or many other) forums; one needs only to abide by the rule/policy.

As has already been mentioned, there is always an option to start a new thread (and link to the previous thread), if you feel you have something of significant value to add.

Previous participants of the original thread will be notified of the link, if that is their preference, and the new thread allows the scope for continued discussion if one has something truly useful to add to the the topic.

These kinds of posts are affectionately called me too posts; these serve only to fill a thread with unnecessary clutter; especially useless when a solution has already been provided and acknowledged.

Just imagine if one hundred well-intending people decided to add “Meee too”, “It works for me”, I had one but the wheels fell off"; I’m sure you get the picture.

Incidentally, over time those numbers can indeed become realistic (depending on the forum) and quite annoying for anyone trying to find useful information in a particular thread. So, it’s quite understandable why ‘Me too’ posts are actively discouraged along with ‘Necro-bumping’.

To the topic at hand, however, I agree that automatic closure of a thread after three days isn’t necessarily ideal for everyone; and I know that the topic has been raised before with due attention given to some concerns; but, for the vast majority of users, it seems to work.

And that’s all I have to say about that.

Cheers.

Aside:- I’m just happy we don’t have the Up/Down Voting B.S. found in some forums. :facepalm:
Edit:- Grammar.

4 Likes

That is how Manjaro forum usually works, but last year the timer was closing topics after 3 hours
Some other Linux fora that I visit have a timer that closes topics 1 month after the first post
But users always have an option to post additional comments:

[quote]
I could create a new thread just to say “hey this thing in this old thread is still happening”, but that’s probably less effective
[/quote]

If the only comment is a “me too” without improving the conversation I would agree that this would not be effective. But for this case (where the accepted solution was not considered relevant to the original problem) it would be better to have a new post so readers do not have to read non-relevant stuff (seems to be usual uninformative hating of pamac) before the new on-topic information. They can follow the back-link if they need some context for comments in new post. And there are now 2 topic in forum searches to lead users to your preferred solution

I usually leave marking a solution to topic to the topic starter, but sometimes I would mark a solution that would be useful for other users

Since you created the topic you should receive notifications of any replies posted and when the topic was marked as solved.
If you did not agree with solution you could move or remove solution marking before the topic is closed
Or send a pm to the person who marked the solution if the topic has been closed
Or send a pm to a moderator/community assistant to re-open topic

2 Likes

Or you could ask a moderator to open the thread for you ;-), If you state your reason this should not be a problem at all.

2 Likes