Timeline for Why do valid questions get closed without providing any help?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 11, 2019 at 10:06 | comment | added | Kulfy | @Melebius According to the blog post: Post authors, privileged users and moderators are shown an expanded notice, which can show additional information that they need to know (e.g., why the question was closed) along with suggested actions that they may want to take (e.g., edit the question). As of now I'm not aware of any meta post specific to off-topic situations but the notice looks like this to other users. | |
| Dec 11, 2019 at 9:07 | comment | added | Melebius | @Kulfy If the note you added to the post is valid, what do other users see? Is there any Meta Stack Exchange post about it, for example? | |
| Dec 10, 2019 at 21:04 | comment | added | Kulfy | Hey Mark, I have edited your post to make it up to date and relevant. But if you think my edits aren't justified, feel free to roll back the edit. Thanks :) | |
| Dec 10, 2019 at 21:02 | history | edited | Kulfy | CC BY-SA 4.0 |
added 114 characters in body
|
| Nov 16, 2019 at 10:37 | comment | added | MalphasWats |
thank you both @DavidShepard and @EliahKagan. I think my issue is that I had no way of knowing that it's a bug before I posted the question. I have managed to work around it by using the proprietary Nvidia drivers, but they come with a bunch of different issues (glitchy weirdness at the bottom of the screen). Unfortunately, your WaylandEnabled=false fix doesn't appear to have worked for me.
|
|
| Nov 11, 2019 at 1:31 | comment | added | Eliah Kagan | @DavidShepard I've commented on the question with a link to your comment here. That should help keep your solution from falling into obscurity before a longer-term way to provide the information is found. That could be by reopening the question if people think it's not a bug, or by linking to a bug report where your solution is mentioned as a workaround. I recommend you edit your meta question to add what you said in your comment--if possible, in somewhat more detail, as the OP didn't say he had an Nvidia GPU, and I don't think every MacBook Pro has one. (Perhaps all of them from 2010 did?) | |
| Nov 10, 2019 at 19:56 | comment | added | David Shepard |
So, here's the thing... It wasn't a bug, it was a mis-configuration. How do I know? Because I had the same problem and I fixed it myself. The solution: edit /etc/gdm3/custom.conf to include the line: WaylandEnable=false This detail matters because the author of the original question states he has an Nvidia GPU, which is broken with Wayland and is what is causing the sleep issue. Too bad nobody will see this because it was down-voted and a comment that is wrong was up-voted. I guess "it's a bug" has been decided...
|
|
| Nov 9, 2019 at 17:34 | history | edited | Kulfy | CC BY-SA 4.0 |
added 65 characters in body
|
| Nov 9, 2019 at 17:00 | history | answered | Mark Kirby | CC BY-SA 4.0 |
