Is anyone else seeing an over use of My computer boots to a black screen, what options do I have to fix it??
Half of the close reviews I see are close, duplicate of that question. That normally wouldn't be so bad, except at least half of those are only loosely related to the "parent" question.
I wonder how many people were scaring off cause there computer is in a state that won't boot, and they come on here to ask for help and people just close their question with a link to My computer boots to a black screen, what options do I have to fix it?
Some are legit duplicates, some are border line, but a few are just people not reading the question.
So rant aside, are people also seeing the same thing, an over use of "My computer boots to a black screen, what options do I have to fix it?"
black screen on boot (DVI) - Radeon 9550/9600/X1050 Series - Lubuntu 13.04 - Not the best posited question, but clearly not a common driver issue. It's a monitor or other issue. The key is after pressing reset it all works. A better course would have been to help the asker clarify the question and get the info we need.
Ubuntu 13.04 boots up with blank screen after update from 12.10 - This might be a legit duplicate, but the linked question isn't helping the asker. It was already closed by the time I saw it. It was in the re-open queue, I advised to open a new question as I thought it would be his best bet. That said a user read the linked question, got nowhere, and updated his question. But the point is. This user is left with no answer, and the perception that,as a community we don't care. I know questions aren't "for one person" but askubuntu isn't a wiki either it's something in between.
It's true that sometimes questions are incorrectly closed as duplicates of the canonical black screen question.
However, as far as I have seen, most such closures are correct. More by percentage, I think, than closures on Ask Ubuntu generally. Futhermore, as I argue/explain below, many of these closures are correct even in situations where closed questions are correctly reopened afterwards.
That master question currently has 24 answers. A question about a black screen on boot--unless it contains enough information for us to know that question and its answers don't apply and for us to know why they don't--should be (and usually is) closed as a duplicate.
If someone has not seen that question, closing their question as a duplicate refers them to it. If they have seen it and it doesn't help (or they go to it from the "possible duplicate" link and it doesn't help), then we still cannot do any better for them unless they explain, in detail, exactly what solutions they tried and exactly what happened.
A black screen on boot question that doesn't exclude the possibility of the canonical question helping should be closed as a duplicate. Once it is edited to exhaustively address all solutions there that could plausibly apply given the parameters of their situation, it can and should be reopened. If we are failing to reopen questions under these circumstances, that would be bad. But I think that, since the reopen queue was introduced, we have not had that problem.
improving the answers to the canonical question (as hbdgaf said) and/or adding new answers to cover other common causes/solutions.
We need to make sure there are answers for the most common causes of the problem. This may already be the case. Perhaps some analysis (using the data explorer) could help shed light on whether or not most black screen problems are effectively addressed by the canonical question.
It should be reasonably easy for people to find answers that are applicable to their situation. Only 3 of the 24 answers there are pointed to by the mini table of contents in the question. Maybe the mini-ToC should be moderately expanded.
If closing in that direction is insufficient to satisfy the needs (and the woes are at least half relevant), we should improve the answer not stop duping to the question.
I would add that displaylink should be forked off and we should have a canonical getting displaylink working q/a pair.