« first day (2726 days earlier)      last day (35 days later) » 

1:42 AM
@Natty tp
 
 
3 hours later…
4:45 AM
no repro (see self-answer)
I don't think this question should be considered a duplicate of the much more specific suggested target.
no repro (see answer)
This question does not seem unclear or off-topic to me.
off-topic - If I understand correctly, the system the OP is asking for help with is not the Ubuntu system.
not off-topic - asking for outdated packages or versions of software on a non-EOL release is not the same as using an EOL release
too broad (some other close reasons might also apply)
not no repro, it should simply be answered
dupe (see accepted answer)
I think it's reasonable for 20k users to vote to delete this closed Kali question at any time.
This question does not seem unclear to me.
 
 
1 hour later…
6:25 AM
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, potentially bad ns for domain in body, +1 more (394): Top Tips For Slimming Down Quickly by carolynlopeny on askubuntu.com
 
6:52 AM
[ SmokeDetector | MS ] Blacklisted website in body (99): DVD shrinking. Problem installing DVD95 Ubuntu 18.04.3 LTS by kebab4me on askubuntu.com
 
7:03 AM
dupe, though perhaps there is a better/additional target
 
8:30 AM
Why have I suddenly got 9 Announcer badges?
@EliahKagan looks more like an audit (where the system seems the question "high quality" and you're supposed to vote to leave open
 
10:17 AM
)
 
 
1 hour later…
1:11 PM
@Zanna It has many edits. The close votes that put it in the queue may be from before some of the edits that made it clearer.
 
@Natty tp
 
@EliahKagan oooh :)
 
@Zanna There had been a bug where the Announcer, Booster, and Publicist badges were awarded only on shared question links, but not on shared answer links. This bug was very recently fixed, causing our missing badges to be awarded.
@EliahKagan Not really a dupe of the question about enabling multiverse, as karel pointed out in a comment, since the software can't be installed from that repo anymore (and the OP's question is still relevant to others). I've gone ahead and just retracted my vote, to avoid having it wrongly duped to that, but it might be dupe-able to the question linked in karel's comment.
@Natty tp
@Natty tp
@Natty tp
@Natty tp
@Natty tp
@Natty tp
 
@EliahKagan oooh :) thanks!
 
1:29 PM
:)
I think this question is clear enough to remain open even though it doesn't say what update(s) coincided with the problem. If this is a regression, we'll probably get other questions about it, in which case many of them can be duped to one of them that has an answer explaining it.
not off-topic - the host OS is Ubuntu (I also don't think it's unclear but that's less obvious)
not off-topic, not really too broad - it should be answered or closed as a duplicate, and it is basically answered in comments so something could be posted based on them (though duping it may be better)
not POB, it can be answered based on facts and specific expertise
not too broad - if it's unclear, specific information should be requested (also, I don't think it's off-topic -- if I understand correctly, the OP is saying the problem temporarily goes away when they restart their computer... and although this still doesn't mean it's not a hardware problem with the screen, or that it's not a hardware problem with the video card/adapter in the computer... I don't think this is definitive)
This question (with this review queue item) is not off-topic, but it seems unclear. Unfortunately it has two OT close votes. Currently it has no other close votes. If it gets at least two unclear votes, and no more OT votes, then if closed, it would presumably be closed as unclear. Is there some reason not to do that at this time? (cc @Zanna)
This question could probably be further improved in an additional edit.
 
[ Natty | Sentinel ] Link to Post Low Length; Low Rep; Unregistered User; 2.0;
 
@Natty tp
We can delete this closed Kali question at any time.
 
2:20 PM
@EliahKagan I'd support closing that as unclear. I actually voted to leave open because I really don't want it to get closed as off-topic
 
dupe (or unclear, or if the information in comments is sufficient to make it clear then that should be edited in... though I think it's just a duplicate)
@Zanna I also voted to leave it open, because I was thinking about the OT votes that had been cast. But looking at it now, I think we should vote to close it as unclear. If it still gets closed as off-topic then I'll vote to reopen it.
I've just VTC'd as unclear.
 
thanks, me too
 
(unrelated) unclear
@Zanna Thanks. One more needed.
unclear, but what specific information is best requested?
 
3:16 PM
This (deleted) post does not seem NAA.
 
hmm yeah
 
Should we consider this type of question as no-repro? Sure the error was because of an extra whitespace but I think many people might miss this and unknowingly adds whitespace. So, no no-repro?
 
@Kulfy That's not no repro.
 
@Kulfy seems highly reproducible
 
3:29 PM
Hmm yeah.
 
On Ask Ubuntu, even problems that actually come down to a typo (without any other conceptually illuminating issue) are not automatically considered no-repro (and the descriptions in Ask Ubuntu user interface, vs. the interfaces of other SE sites where typos are automatically no repro, differ accordingly). But even if we had the view of no repro that is taken on Unix & Linux or Stack Overflow, I believe that question would not be no repro.
@Natty fp - not quite link-only, and it states a possible explanation... but it would benefit from expansion
 
@EliahKagan Yeah. I wasn't sure since I have seen many typo questions are closed as no-repro and also the extra whitespace isn't visible without going into the markdown or selecting the text.
 
On Ask Ubuntu, it is uncommon that a question that turns out to be a typo should be closed as no repro. (It only happens when there is some other reason it qualifies as no repro, though that other reason could potentially be related to it being about a typo.) If we have questions that are closed as no repro but that can be reproduced and are not clearly of only transient relevance, those questions should be reopened.
One thing I've noticed on Unix & Linux is that questions where one must have conceptual understanding to know that something is a typo or why the typo has the reported effect are closed as no repro, over and over again, sometimes for the same sort of typo with the same conceptual issue, which keeps not getting meaningfully answered, so it keeps happening again and again.
I think this actually accounts for a considerable portion of the appearance that Unix & Linux has higher quality standards than Ask Ubuntu -- they close and delete more answerable questions that could be answered or duped in a conceptually illuminating way.
(I'm not saying that there are not some ways in which Unix & Linux really does have higher quality standards than Ask Ubuntu, since I think there are. But I don't think the appearance that they do, or the widespread belief that they do, actually has much to do with the ways in which they do.)
 
I haven't observed similar problems on Stack Overflow, though. They seem to interpret their typo → policy in a more nuanced way. OTOH, SO is huge. My observations may have little to do with the actual trends.
@Natty tp
@EliahKagan * their typo → no repro policy
 
3:51 PM
@EliahKagan nice hat
 
Thanks.
 
@Natty tp - it's a thanks post about the previously posted answer
 
4:43 PM
unclear - some specific information should probably be requested in addition to closing it
 
 
1 hour later…
6:10 PM
no longer needed, a not-very-useful and edgy comment
I left a comment below, supposed to be a response, but I would remove it if / when the aforementioned comment is removed.
The previous comments are not very useful either flagged all of them.
 
 
2 hours later…
 
1 hour later…
9:44 PM
@Natty tp
@Natty tp
 
10:22 PM
@EliahKagan The question that it answers is a duplicate too, except that in the duplicate question the list is explicitly described in several answers instead of being linked to by a hyperlink.
 
11:14 PM
@karel VTC'd
 
[ Natty | Sentinel ] Link to Post Low Length; No Code Block; One Line only; Low Rep; Unregistered User; 3.0;
 
[ Natty | Sentinel ] Link to Post Low Length; No Code Block; Low Rep; 2.0;
 
11:31 PM
 
[ Natty | Sentinel ] Link to Post Low Length; No Code Block; One Line only; Low Rep; 3.0;
 
[ Natty | Sentinel ] Link to Post Low Length; No Code Block; 1.0;
 
11:46 PM
 
[ Natty | Sentinel ] Link to Post Low Length; No Code Block; Low Rep; Unregistered User; 3.0;
 

« first day (2726 days earlier)      last day (35 days later) »