Timeline for Why was this thread closed?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 14:35 | history | edited | CommunityBot |
Commonmark migration
|
|
| Dec 4, 2013 at 20:58 | comment | added | JoshuaD | @Braiam:I am really confused with what you have said.Where in the rules does it say that any power-related issue is a bug? Where is the rules does it say that "problems of nature X are bugs"? It seems possible to me that this is a configuration issue. I tend to believe you that it's a bug, but I think it would be best to leave the possibility open that it's not, unless you are 100% sure. Are you 100% sure? If so, how? Either way, I have made my case. I think you are handling this issue incorrectly and for the sake of the boards I have asked you to reconsider.It's your choice. Thank you again. | |
| Dec 4, 2013 at 20:52 | comment | added | Braiam | @JoshuaD We live by the rule, abide by the rules, and do not bend the rules. The rules says that your question is about a bug, henceforth your question is Offtopic. | |
| Dec 4, 2013 at 20:50 | comment | added | Braiam | @JoshuaD OK, let me put this clear. Will we spend our time trying to figure out why is or not is a bug instead of you reporting a bug and then comming back with a definitive fix for all the people that use Ubuntu? I'm sure that most of AU users and people that answers questions will say no. | |
| Dec 4, 2013 at 20:47 | comment | added | JoshuaD | Anyway, I think you guys made the wrong call here for the reasons I outlined in my previous comment.Guessing that something is a bug is an answer (which can be falsified by another poster). Treating it like that seems like the better method to me. As you are the moderators here, please consider it. Especially since no one has said "I am 100% certain this is a bug" In either case, thank you for your assistance,and thank you for what you do to keep this place running.I disagree with this decision, but I am sure that your jobs aren't easy(and thankless to boot)so thank you for doing your best | |
| Dec 4, 2013 at 20:46 | comment | added | Flyk | "StackExchange (ergo AskUbuntu) is for questions that has 1 valid answer and that that answer will be still valid for the years to come. [...] here's not the right place to solve them." is actually incorrect, the Stack Exchange system actively encourages multiple answers offering different methods of completing the same task so that the best method as determined by the community is upvoted to the top. This is clearly shown on the about page for every Stack Exchange site. Bugs are still off topic though regardless. | |
| Dec 4, 2013 at 19:13 | history | edited | Seth | CC BY-SA 3.0 |
added 2 characters in body
|
| Dec 4, 2013 at 18:25 | comment | added | JoshuaD | "StackExchange (ergo AskUbuntu) is for questions that has 1 valid answer and that that answer will be still valid for the years to come. [...] here's not the right place to solve them." It really seems like you should have submitted "This is a bug for reasons X and Z. The proper venue to resolve this is <link>" as an answer to the question. I would have said thank you, I would have upvoted and accepted your answer, other users could have learned from it, and the thread would be open for @JohnSmith to come forward and say "No, it's not a bug! Edit line 55 of whatever.config! It worked for me!" | |
| Dec 4, 2013 at 18:25 | comment | added | Braiam | @JoshuaD if it has the possibility of being a bug, you should report it in LaunchPad then the big guys there will told you either it is indeed a bug or you are just doing things wrong, and your question in particular smells a bug however I see it. | |
| Dec 4, 2013 at 18:24 | comment | added | Braiam | @JoshuaD comments are not meant for discussion about the question, but to inquire the poster more information/clarification. And the explanation was in the same close reason and dobey was nice enough to tell why was he voting to close the qeustion. | |
| Dec 4, 2013 at 18:21 | comment | added | JoshuaD | In either case, closing the thread doesn't appear to do any good. It inhibits the possibility of an answer coming forward and it prevented me (without doing a ton of additional communication) from understanding that the issue is probably a bug. | |
| Dec 4, 2013 at 18:20 | comment | added | JoshuaD | That's some useful information reasoning. I wish you had posted it in the discussion thread for me to review. If you had (rather than voting to simply close the thread with no explanation) I would have been grateful rather than frustrated. I also don't know that you're right. You used phrasing like "Problems [like this] are normally problems with..". Well maybe this isn't the normal case. Maybe @John_Doe has the solution that will fix my problem and now he can't post it. Or maybe you're right, and the other posters who had a similar problem would have benefited from reading this. | |
| Dec 4, 2013 at 18:07 | history | answered | Braiam | CC BY-SA 3.0 |