-2

I run into this problem often. Case in point:

19.10 seems to have broken suspend on my MB Pro

This user has a reputation of 111, appears to be an active contributor, and actually has the same problem I came here looking for answer to, along with possibly 84 other people, who have viewed his question. It's incredibly unhelpful.

||||||
15

The reason for the close is given in the blue box above the question body

"Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues."

Note: This banner is visible only to the questioner and users with 3000+ reputation points

Bugs are explicitly off topic here, as per the help, meaning this is not a "valid" question.

You state "It's incredibly unhelpful" but it is quite the opposite. Firstly the question had no answer, so won't be helping you or anyone else find a solution but the reason for closing gives the link to the correct place to report the bug and that is very helpful, seriously, go and report it on Launchpad, the developers will see it and they are the ones who can fix the issue, the more of you that go and report a bug, the more priority the devs will give to it and the quicker it will be fixed.

||||||
  • 1
    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... – David Shepard Nov 10 '19 at 19:56
  • 4
    @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?) – Eliah Kagan Nov 11 '19 at 1:31
  • 1
    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. – MalphasWats Nov 16 '19 at 10:37
  • 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 :) – Kulfy Dec 10 '19 at 21:04
  • @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? – Melebius Dec 11 '19 at 9:07
  • 1
    @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. – Kulfy Dec 11 '19 at 10:06
-2

I agree that others should have asked to see content of journalctl -b-1 in comments. Then after reason for broken suspend was ascertained posted an answer if possible or advised to file a bug report if not possible to fix.

You have to appreciate these days there are many many questions being asked without enough volunteers to carefully and thoroughly address them. Subjectively I think things have gotten worse since mods went on strike over that legal thing.

The OP could have gamed the system by simply saying "suspend is not working" instead of saying "suspend broken after 19.04 to 19.10 upgrade". It seems silly but many a question will be answered when saying "X is broken". However if you say "X is broken because of Y" then they will say file a bug report against "Y". In reality when looking at journalctl -b-1 it may say the problem is caused by "Z" and totally unrelated to "Y".

I guess we can call this the X-Y-Z problem of prematurely closing questions.

||||||

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .